Jason gave a good explanation, but I'll give a shorter one with some clairifications:
1) RC2 unstable is what should be 1.0 RC2 once merged with HEAD. After that, bugfixes and a 1.0 release. 2) RC2 unstable only contains fixes for the multiple creation of Jelly contexts and ant projects for plugins, butting back to one ant project in total per goal attainment and one context per plugin per execution. This fixes the reactor memory leak. It was largely based on Jason's branch, although isolated to changes in the plugin manager, obviously. 3) all the other stuff Jason did is good cleanup/refactoring and will make Maven easier to embed (and more importantly understand and develop on :), and it seems it will all be rolled into post-1.0 now, 1 piece at a time while we ensure everything continues to work as it used to. 4) I implemented property inheritence within the current Jelly infrastructure. It hasn't received much testing yet, but should work. It also inherits multiple levels of the POM, maven.xml and the properties. There is a test project in the branch. Hope this is less confusing :) Are we all in agreeance that 1) and 3) are basically the roadmap for maven-core through 1.0 and 1.1? If so, I might embellish a bit, put it on the wiki, and make sure JIRA is setup appropriately. Cheers, Brett > -----Original Message----- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: Tuesday, 18 November 2003 2:20 AM > To: 'Maven Developers List' > Subject: RE: rc2 unstable > > > Guys, sorry to ask again but I have trouble understanding > what's in those branches. What is the status with properties > inheritance? Is that in rc2 unstable? Is it going to be > rolled in anytime soon? What is rc2 unstable? Is it based on > a completely new Maven core (plexus). If so, how could you > merge it with head without breaking everything? > > Thanks > -Vincent (a bit confused :-)) >
