JBossDeveloper

Ideally, daily build should have been there already but I wrote the script so that it happens only after compile and testsuite runs happen successfully. Since there has been problem with testsuite, it does not go to that point. I am going to change this to do it after successful build and not depend on testsuite run.

Ouch, I think I like the after successful testsuite idea better. I would rather wait and deal with the firewall issue for now and potentially broken code. It just seems like the better part of wisdom. At least with the trunk I know it may not pass.

BTW, is that integration or unit test or both? I hope the stuff at least passes unit tests before being checked in.

It's all unit tests that are available portal codebase.

Nothing to do with bugs bug since portlets just produce page fragments have you thought about supporting Ajax requests for action and view for a portlet?

Maybe a parameter to tell the Portal container to skip page assembly and just pass back the fragment?

Would seem to be a natural extension of the Portal idea and it would lighten the portal and speed up the response time a lot.

Yu can see today's build at http://cruisecontrol.jboss.com/cc/artifacts//jboss-portal-trunk-build. Please let me know if you run into any issue with this.

Breaks here:

output:

BUILD FAILED
C:\workspace\jbportal\trunk\tools\etc\buildfragments\buildmagic.ent:273: The following error occurred while executing this line:
C:\workspace\jbportal\trunk\workflow\build.xml:170: C:\workspace\jbportal\trunk\workflow\output\resources\portal-workflow-jar not fo
und.

also, you created the tar two directories down from where it is created from the svn checkout /jbportal/trunk

"prabhat.jha@jboss.com" wrote:
It's all unit tests that are available portal codebase.

I don't know what you are talking about the 2 directories down, but i just tried:

wget http://cruisecontrol.jboss.com/cc/artifacts//jboss-portal-trunk-build/jboss-portal-trunk-src-20070220.tar.gz
tar zxvf jboss-portal-trunk-src-20070220.tar.gz
cd build
build.sh clean
build.sh

 ==
 ==
 == Finished 'most' in module 'core-samples'.
 ==
 ==============================================================


BUILD SUCCESSFUL
Total time: 1 minute 0 seconds
[theute@localhost build]$

build.bat doesn't work at all so I used ant deploy

calling ant directly or through the build does not change anything, you just need to have the correct ant libraries. Look for errors.

C:\workspace\jbportal\trunk\build>goto :EOF

C:\workspace\jbportal\trunk\build>if exist C:\workspace\jbportal\trunk\build\..\tools\bin\build.bat call :call-script & goto :EOF


C:\workspace\jbportal\trunk\build>call :debug Executing C:\workspace\jbportal\trunk\build\..\tools\bin\build.bat

C:\workspace\jbportal\trunk\build>if not x == x echo build.bat: Executing C:\workspace\jbportal\trunk\build\..\tools\bin\build.bat

C:\workspace\jbportal\trunk\build>goto :EOF

C:\workspace\jbportal\trunk\build>call C:\workspace\jbportal\trunk\build\..\tools\bin\build.bat
=true was unexpected at this time.

Closest I found to an explanation was this:

http://www.robvanderwoude.com/index.html

Nope, used your ant in the tools\bin directory, no difference same error

no errors until it looks for the jar file

It is such a convoluted build it is hard to debug. Where is the point in the build where C:\workspace\jbportal\trunk\workflow\output\resources\portal-workflow-jar is produced?