Brett Porter pisze: > [X] (A) All plugin versions must be specified by the project or its > parent hierarchy somewhere, at the cost of some verbosity (though we > should look at ways to make this easier/smaller/etc per the current > discussion) > [ ] (B) Retain the current behaviour, but make using the enforcer a best > practice to do the above, or some other control mechanism such as having > the repository manager handle the available plugins > [ ] (C) No opinion > [ ] (D) Undecided > [ ] (E) Other (please specify)
I support Jason's Dillo and Arik's Kfir opinions. At Apache Cocoon we have been suffering far too much from Maven's unpredictability in general. Last versions of Maven (2.0.6+) plus more knowledge about best practises in Maven made our builds controllable and very stable. The only remaining part are plug-in versions, exactly. It's worth to say that many of our brilliant members were so dissatisfied with broken builds driven by Maven that nobody had idea what's wrong that they started to claim that Cocoon is dying because of Maven. Many times, it was caused by our misuse or misunderstanding of Maven's philosophy but it was a Maven that allowed us to fall into these pitfalls. We are more clever now and fortunately enough, we are pretty satisfied with Maven today even if we have a lot of crap in our poms due to numerous bugs in Maven. My opinion is that Maven's community should be also more clever and should not allow people to screw their builds. -- Grzegorz Kossakowski http://reflectingonthevicissitudes.wordpress.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
