FYI, we already do this for AOP.
Adrian Brock wrote:
On a related issue. I really want to bite the bullet
on sorting out the jboss-common dependencies and making more
managable chuncks for standalone projects to eat.
I've been waiting for the ongoing build changes to stabalise
before doing this in jboss-head.
This would allow us to properly have one code base for things like
JBoss Logging, JBossXB, JBossAOP, JBossMC
with 4.0.x and 5.0.x consuming these projects based on their
own versions and branches rather than time consuming and
potentially unreliable backports.
This would also fix the potential problems with
JBoss Cache, Remoting, Seam, etc. compiling over unknown
versions of these libraries copied at some point in the
past from the JBossAS build.
My question is how does this impact the work being done for the Maven
build? The last time I looked, only a minimal Maven build was done
which was essentially just building the projects that I want
to "fix" (fix as in make not broken Scott :-).
--
Bill Burke
Chief Architect
JBoss Inc.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
