On Fri, Jul 17, 2009 at 1:07 AM, ant elder<[email protected]> wrote: > > I really don't think we should do that. Having the plugins be part of > the build makes the build unstable, we've seen numerous problems > caused by that in the past, the build is simple and stable now and I > think we're forgetting how good it is now compared to what its been > like in the past. What I think may help would be to have a look at the > more general release processes, PMC member obligations, and voting > etc. I'd planned to start a discussion about that after M3 is done. > > ...ant >
Maybe the instability in the past was due to these plugins were being developed/enhanced, but other then that, the only issue was that you might need to run the "setup" profile in trunk to get the latest plugin (mostly the eclipse-compiler) built before running a full build. Well, if the community prefer to leave the maven-plugins as an apart sub-project, how about removing the obsolete ones (maven-java2wsdl-plugin, maven-wsdl2java-plugin, maven-zip-plugin, maven-tuscany-plugin), and somewhat bundle together the release of the other 3 bundles with the 2.x releases ? At least this wouldn't cause less last minutes issues during the 2.x release? Thoughts ? -- Luciano Resende Apache Tuscany, Apache PhotArk http://people.apache.org/~lresende http://lresende.blogspot.com/
