"[EMAIL PROTECTED]" wrote :
| ${somedir}/JBossAS - the main integration build
| ${somedir}/test1 - test1 component
| ${somedir}/test2 - test2 component
| ${somedir}/tools - the tools directory containing jboss/tasks.xml
|
I notice that you declared jboss-common.jar as a dependency of JBossAS, so I
assume you see some of the existing components essentially becoming thirdparty
libraries of the AS -- being downloaded from the repository along with log4j.
At the same time, other components (test1 & test2) are checked out of CVS and
compiled from source.
Why the difference? Why not just have all the existing components become
external libraries?
If all of the existing components were migrated to standalone projects, they
could be integrated into the AS just like any thirdparty library. Their
artifacts would be pulled from the repository just like log4j.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3860643#3860643
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3860643
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
