The 'all' target and the 'most' target are the same except that 'all'
calls 'modules-all' and 'most' calls 'modules-most'. Anyone know the
difference between the two (modules-all and modules-most)?
Hany Mesha wrote:
It turned out that build clean then build all doesn't copy
jboss-remoting.jar
Sent: Wednesday, April 05, 2006 6:55 AM
> To: jboss-development@lists.sourceforge.net
> Cc: QA
> Subject: Re: [JBoss-dev] jboss-head, Testsuite for all
> configuration fails
>
> The 'all' target and the 'most' target are the same except that 'all'
> ca
Documenation is also done by all.
On Wed, 2006-04-05 at 09:55 -0400, Tom Elrod wrote:
> The 'all' target and the 'most' target are the same except that 'all'
> calls 'modules-all' and 'most' calls 'modules-most'. Anyone know the
> difference between the two (modules-all and modules-most)?
>
>
It turned out that build clean then build all doesn't copy
jboss-remoting.jar to the server build lib directory causing this
error. I overcome the issue by copying the above jar to
build/output/jboss-5.0.0.alpha/server/all/lib directory.
Now I see the error reported on cruise control but only on m
Running the all config from a clean check out and build is fine (at
least for booting). Running the testsuite does give an error when
booting the all configuration (during jboss-all-config-tests target),
but logs indicate is due to port 1098 already being in use. Saw the
same on the cruisecon
