On Fri, Jul 17, 2009 at 3:17 PM, Luciano Resende<[email protected]> wrote: > 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 ?
I think the instability was caused by more than plugins just being developed/enhanced it was caused by the way the build was building the plugins as part of the build but running against the previous built verison, and having the build using snapshot releases of the plugins. The result was lots of inconsistency in peoples build environments, intermittent problems, and "have you tried mvn -U" type emails. The setup profile didn't fix this, and it breaks maven standard build conventions. I'm not sure I understand the dislike of separate plugin releases so wonder if i'm missing something? Its the normal way of doing maven projects and they're really easy to release now we have it set up, the only hard bit is getting the three +1s on the release vote. The zip plugin could be removed (and I've delete it now) but the others are needed aren't they? Just not released yet, or are we not needing the tuscany wsdl tools anymore and going to just use the jaxws tooling? ...ant
