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)?
Scott M Stark wrote:
That is fine, but I'm creating a jbossbuild script that will generate the legacy thirdparty structure from the repository to get rid of the existing thirdparty cvs tree. I would like to have the option of not having to checkout the legacy thirdparty tree as part of the jboss-4.0/jboss-head co and instead build this on demand based on a synchronize target to avoid having to duplicate where thirdparty jars need to be checked in. I guess this will require a new cvs module alias (at least for jboss-4.0) to avoid breaking the build of existing releases.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tom Elrod
Sent: Monday, May 09, 2005 1:34 PM
To: [email protected]
Subject: [JBoss-dev] creating jboss thirdparty directory
Since I am now doing all new development in the JBossRemoting module, which is stand alone, I would like to make a few changes as to how jboss-head picks up the remoting code.
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
[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_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
