Yes, go ahead. After I finish the 4.0 thirdparty setup I'll migrate it to the jbossas build on head as well. The code that will continue to live in jbossas like the legacy ejb container, jbossmq, etc. should be copied into the jbossas module with its cvs history to get rid of the modules file usage as well to complete this.
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Tom Elrod > Sent: Tuesday, May 10, 2005 8:58 PM > To: jboss-development@lists.sourceforge.net > Subject: Re: [JBoss-dev] creating jboss thirdparty directory ... > > I think we are there. There is already a jbossas module > defined with nothing but the new build in it. Remoting is > ready to make this move (no better time actually). If you > give the green light, I will execute what I have described > below and we will be on our way to this new path. > > As other projects break off, they can do the same. I think > with the new build process, it would also be a big help to > network as will have modular, versioned components that will > be easier to do patch updates for. > ------------------------------------------------------- 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 JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
