So this is item 3 on Ruel's list to look into. It's related to item 1. as I explained its usage to Ruel.
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Adrian Brock > Sent: Thursday, February 09, 2006 8:14 AM > To: jboss-development@lists.sourceforge.net > Subject: Re: [JBoss-dev] On the edge of the Maven cliff > > The problem I don't see addressed (and the main reason why I > started the jbossbuild prototype) is to have a top level > which includes multiple projects. > > e.g. I wanted people to be able to do something like: > > <build> > <component name="JBossAS" download="binary" > quality="LastGoodTests"> > <component name="EJB3" download="source"/> > </component> > <component name="Seam" download="source"/> </build> > > This would checkout the last binaries for JBossAS that passed > the testsuite (except EJB3 which is latest source) and also Seam. > > You would then be able to build a Seam environment with just the > EJB3 and Seam sources. > > i.e. the developer only has to worry about the problems with > the stuff he is working on, rather than figuring out why > something unrelated doesn't compile/work. > > Instead, the jbossbuild project morphed into a mechanism to > download thirdparty binaries with buildmagic still used for > the main build. > ------------------------------------------------------- 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
