Part of the problem is everyone running around trying to get work done on multiple branches while Ruel is trying to baby step new build setups in. I think we need to get to a point where we just say head is going to be refactored and potentially broken for an extended period of time while we refactor it for:
- build structure - module coarseness and invalid dependencies (like the server/security issue) - refactoring for integration api introduction The production branches have to remain stable during this. > -----Original Message----- > From: Adrian Brock > Sent: Friday, February 10, 2006 4:43 AM > To: jboss-development@lists.sourceforge.net > Cc: QA > Subject: RE: Ongoing build changes: was RE: [JBoss-dev] On > the edge oftheMaven cliff > > 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. :-( > ------------------------------------------------------- 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
