The jboss-remoting.jar is now in the thirdparty/jboss/remoting/lib directory and is a library instead of a module (as seen from the buildmagic view). This means that references to the jboss remoting jar should be made from the library classpath and not the dependent module classpath.
Files changed (and checked in) for this:
aspects/build-test.xml aspects/build-test50.xml aspects/build.xml build/build.xml ejb3/build-test.xml ejb3/build.xml jmx-remoting/build.xml server/build.xml testsuite/build.xml testsuite/deprecated-build.xml tools/etc/buildmagic/libraries.ent tools/etc/buildmagic/libraries.xml tools/ent/buildmagic/modules.ent tools/ent/buildmagic/modules.xml transaction/build.xml webservice/build.xml
The integration code between JBossAS and JBossRemoting now lives under the jbossas module in a subdirectory called remoting. When this is built, it will yield a jbossas-remoting.jar.
The full jbossas server build will put the jboss-remoting.jar and jbossas-remoting.jar in the default & all lib directories.
The only build file I did not change was for jmx\build.xml, since it uses a custom jboss-remoting.jar under its resources directory.
I will be updating the jboss-remoting.jar in the thirdparty lib directory as I add features and will notify everyone before making an update if there are ever any API changes that may impact dependent projects.
------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
