You will just need to checkout the container/dependency/kernel projects manually (they are no longer a part of the jboss-head alias). Using whatever tag was added for that release.
Other than that, it will be the same. It shouldn't affect AOP. Only AOP2.0 (which hasn't been released yet) has a dependency on container. On Tue, 2006-05-02 at 16:20 -0500, Ryan Campbell wrote: > Will removing these modules from jboss-head prevent previous releases of > ejb3, aop & microcontainer from being built? > > I guess the answer is no, but the checkout instructions have changed? > > -----Original Message----- > From: Adrian Brock > Sent: Tuesday, May 02, 2006 2:21 PM > To: Scott M Stark > Cc: Adrian Brock; Ryan Campbell; QA; > jboss-development@lists.sourceforge.net > Subject: Change to HEAD Build. Microcontainer now binary dependency. > WASRE: jboss-head-jdk-matrix Build Failed > > This has been done, except the cruisecontrol changes. > I've left some other issues open for a more complete standalone build: > http://jira.jboss.com/jira/browse/JBMICROCONT-87 > > The updated build instructions are here: > http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMicrocontainer > if you already have a previous head checked out, the only change > is that these projects won't automatically be a part of the main build. > > The version of the microcontainer used is a snapshot from > earlier this afternoon. Which will be updated to 2.0.0M1 > when that is finalised. > > On Tue, 2006-05-02 at 16:26 +0200, Adrian Brock wrote: > > On Tue, 2006-05-02 at 09:07 -0500, Scott M Stark wrote: > > > > It would potentially be possible to require the MC projects > > > > to be developed against head while still being thirdparty > > > > binaries in the main jboss-head build. > > > > i.e. You would checkout the projects separately into the head > tree. > > > Meaning just dropping them from the jboss-head module alias and > manually > > > checking > > > them out into it? If that is the case this should just be done > > > independent of the svn move just to decouple the mc code from jboss5 > as > > > currently the only user of these is ejb3 as far as I can see. We > just > > > need the mc artifacts pushed out to the repository. > > > > > > > Ok, I'll do this. If you want to use JDK5 features, we > > should also look at make jboss retro binaries. > > > > I'll make JBoss-Head build on the JBossMC-1.0.2.GA > > binaries. Besides the bean deployer in varia, only EJB3 > > is using it until JBossMC-2.0.0M1 is finished. > > > > Then I'll update the WIKI page on how to develop > > the microcontainer until we have a proper standalone build. > > > > Cruisecontrol will also need updating once this is done. -- xxxxxxxxxxxxxxxxxxxxxxxx Adrian Brock Chief Scientist JBoss Inc. xxxxxxxxxxxxxxxxxxxxxxxx ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
