So you want?
1. The jboss-head/remoting directory and its contents (which now only contains integration code on my local disk) to be moved under the jboss-head/jbossas directory (including src/main and src/tests).
2. Then update the jbossas build so it will be its new remoting subdirectory.
3. Remove the jboss-head/remoting directory (thus making it dead in jboss-head). I can't remove the _jboss_remoting module reference from within the jboss-head project definition because of previous versions will still need to have it available, right? (based on some tag earlier on jboss-head).
4. Change the component definition for remoting to use module="JBossRemoting" instead of module="jboss-remoting" within the new build.
Scott M Stark wrote:
We need to stop using the cvs module as the merge mechanism. I don't think integration code should be a seperate cvs module. I would view it as code inherent to jbossas, so the integration code for the various services should just be subdirectories of the jbossas module:
jbossas/build jbossas/microcontainer jbossas/naming jbossas/remoting ...
I'm never going to use the _jboss_remoting by itself, so it should not exist as a top level module.
We also need a cvs module naming convention as I have no idea what all this crap is: [EMAIL PROTECTED]:~$ ls -1 /cvsroot/jboss/ admin aop applications Attic blocks-jboss build build-jboss buildmagic cheese cluster-jboss common common-jboss console container contrib CVS CVSROOT docbook-support ecperf hibernate javassist jaxrpc jboss jboss-3.2 JBoss-3.2 jboss-admin-console jboss-all jboss-aop jboss-aop-eclipse jbossas jboss-aspects jboss-blocks jbossbuild jboss-cache JBossCache jboss-common jboss-compatibility jboss-console jbosscx jboss_deployment jboss-deployment jboss-docs jboss-ejb jboss-ejb3 jboss-ejb3x jboss-head jbosside jboss-j2ee jboss-j2se jboss-jms jboss-mail jboss-management jboss-mbeans jboss-media jbossmq jbossmqadmin jbossmqbench jbossmx jboss-persistence jbosspool jboss-portal jboss-portal-docs _jboss-portal-setup jboss-portal-thirdparty jboss-portal-tools jboss-profiler jboss-remoting JBossRemoting jboss-seam jboss-site jbosssx jboss-system jbosstest jboss-tomcat jboss-transaction jboss-v3.2.x jboss-xdoclet jbportal-upgrade jmx jmx2 jmx-remoting jnp jrunit junitejb manual microkernel netboot-demo newsite nukes nukes-2 nukes-2-thirdparty nukes-docs nukes-thirdparty nukes-tools nukes-website opennms person pn-website repository.jboss.com specj sun-ejb system2 test thirdparty tools tools-win32 webservice website website-forums website-snapshots website-survey wiki2html xpetstore-ejb3 xpetstore-ejb3.0
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tom Elrod
Sent: Tuesday, May 10, 2005 11:42 AM
To: [email protected]
Subject: Re: [JBoss-dev] creating jboss thirdparty directory
I have the old build ready locally for both the jboss-head and JBossRemoting. Now I need to change the CVSROOT/modules file. I want to take the _jboss_remoting module (the current one under jboss-head) and rename the alias to something like remoting-integration. Could really use suggestions for a better name. This will contain only the integration code between JBossRemoting and JBossAS.
Then I will declare another entry for JBossRemoting, which has the old alias remoting. This is so the new build will work. I will also need to add a new component for the remoting-integration.
So, the new CVSROOT/modules would have the following entries:
_jboss_remoting -d remoting-integration jboss-remoting-integration
JBossRemoting -d remoting jboss-remoting
Will also have to change the component declarations within the new build to have:
<component id="remoting-integration"
module="jboss-remoting-integration"
version="5.0-SNAPSHOT"
>
<artifact id="jboss-remoting-integration.jar" release="server/all/lib"/>
</component>
<component id="remoting" module="jboss-remoting" version="5.0-SNAPSHOT" > <artifact id="jboss-remoting.jar" release="server/all/lib"/> </component>
I don't think the JBossRemoting project is getting built via cruise control, so the jboss-remoting.jar snapshot will not be getting updated until we can get this added. Will also need to have it add jboss-remoting-integration.jar as well.
Is there anything else I am missing for this to work? Once this change is made, am not sure exactly what people will need to get the update view of the source. Go to jboss-head root directory and run 'cvs co remoting'? Guess will need to do same thing for thirdparty (to get thirdparty/jboss/remoting/lib/jboss-remoting.jar)?
------------------------------------------------------- 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_ids93&alloc_id281&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
