So the first change in perspective is that there is no jboss-head, jboss-4.0, etc as these are hacks around the fact that the jbossas definition is a composite of independent modules that could not be maintained from a versioned build descriptor because of the mistep of using the cvs modules file. That was a big mistake.
So where we want to get to is that there is a jbossas cvs module that is the codebase for the jbossas server project. Its build files which can be versioned incorporate the thirdparty dependencies and associated inherent and integration code for the given jbossas version. If we had escaped from the buildtragic scheme long ago, I would checkout the jboss-4.0.x jbossas codebase using: cvs co -r Branch_4_0 -d jboss-4.0 jbossas the head version would be checked out using: cvs co -d jboss-head jbossas Now the problem is how we get there. Its going to take the creation of a jbossas cvs module and copying the existing inherent and integration code modules into jbossas so as not to lose cvs history. As features like remoting and cache are broken out, we add the integration code to the jbossas module, and import the binaries using component references. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Tom Elrod > Sent: Tuesday, May 10, 2005 12:55 PM > To: [email protected] > Subject: Re: [JBoss-dev] creating jboss thirdparty directory > > 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. > ------------------------------------------------------- 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
