First, I would like to make the remoting code visible to jboss-head as a binary. For the old build, this means adding it to the thirdparty directory and changing the old build scripts for the modules that need remoting to include the remoting jar from the thirdparty directory.
I was going to create a new directory that looked something like:
thirdparty/jboss/remoting/lib/jboss-remoting.jar
For the new build, can just include the pointer to the repository for the remoting jar.
I also want to keep the jboss-head/remoting directory, but make it contain the code for integration between JBossAS and JBossRemoting. So I will be removing almost all of the code that is currently there (which is the core remoting code currently).
Please let me know if this is going to be a problem or if you have any other suggestions on how to do this.
Thanks.
-Tom
------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. Get your fingers limbered up and give it your best shot. 4 great events, 4 opportunities to win big! Highest score wins.NEC IT Guy Games. Play to win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20 _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
