Its done (will send out e-mail about the changes in a minute). The only issue now is exactly how we want to include jboss binaries within thirdparty. Right now, the entry brining in the jboss-remoting.jar is defined as:

_thirdparty_jboss_remoting   -d jboss   thirdparty/jboss

and _thirdparty_jboss_remoting is included in the _jboss_thirdparty definition. This means that a checkout of jboss-head will create:

thridparty/jboss/aop/lib/jboss-aop.jar
thridparty/jboss/aop/lib/jboss-aspect-library.jar
thridparty/jboss/plastic/lib/
thridparty/jboss/remoting/lib/jboss-remoting.jar

As far as I can tell, the thirdparty/jboss/aop is for 4.0 and is defined as:

_binary_jboss_aop   -d jboss-aop   thirdparty/jboss/aop

so that there is

thirdparty/jboss-aop/lib/jboss-aop.jar
thirdparty/jboss-aop/lib/jboss-aspect-library.jar

Should I leave jboss-head the way it is or change to match the way aop is included in 4.0? Really just down to whether we want a bunch of thridparty/jboss-XXX directories or thirdparty/jboss/XXX with some of the XXX directories not being needed.


BTW, looks like HEAD build is broken due to:

C:\tmp\jboss-head2\jboss-head\aspects\src\main\org\jboss\aspects\security\AuthenticationInterceptor.
java:43: cannot resolve symbol
symbol : constructor SecurityException (java.security.GeneralSecurityException)
location: class java.lang.SecurityException
throw new SecurityException(gse);



Scott M Stark wrote:
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: [email protected]
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 [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

Reply via email to