We already have a task for it http://jira.jboss.com/jira/browse/JBBUILD-58
But I don't believe anybody has really looked at what it will take in general. My comments on the issue in the forums are mainly based on what I remember seeing when I was fixing other things. None of the JIRA tasks contain a link to these discussions. Which is my fault. :-( On Fri, 2006-02-10 at 07:25, Scott M Stark wrote: > I don't see stabilization happening though as we still have the pending > maven move and restructing to have a common module structure and > potentially splitting up existing projects to better match the maven > ideal. Let's just define how we want commons broken up with Ruel in the > loop so he can chase it. > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On > > Behalf Of Adrian Brock > > Sent: Friday, February 10, 2006 2:47 AM > > To: jboss-development@lists.sourceforge.net > > Subject: Ongoing build changes: was RE: [JBoss-dev] On the > > edge of theMaven cliff > > > > 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 :-). > > -- > > xxxxxxxxxxxxxxxxxxxxxxxx > > Adrian Brock > > Chief Scientist > > JBoss Inc. > > xxxxxxxxxxxxxxxxxxxxxxxx > > > > > > > > ------------------------------------------------------- > > 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 > > > > > ------------------------------------------------------- > 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&kid3432&bid#0486&dat1642 > _______________________________________________ > JBoss-Development mailing list > JBoss-Development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jboss-development -- xxxxxxxxxxxxxxxxxxxxxxxx Adrian Brock Chief Scientist JBoss Inc. xxxxxxxxxxxxxxxxxxxxxxxx ------------------------------------------------------- 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
