I absolutely agree but it's not that simple. When we introduced the concept of providing defaults in 2.0.9, we had to maintain the status quo. That is we had to lock down at the current versions of plugins to avoid reverting people. This was the line in the sand as they say. We then have a policy of not using releases that are less than 30 days old and no alpha/betas. However some things like release were beta when the line was drawn and so we should follow those up provided they meet the 30 day rule. After that, we wouldn't pick up betas again. For example if compiler 2.1-beta came out, we would keep the default at the current 2.0.2 until compiler 2.1 was released.
Hope that clarifies it. Furthermore, we absolutely do not recommend that people rely only on the defaults. You should take control of your own destiny and lock down to the versions you have tested with. This is the only way to guarantee reproducibility in the future. Further, the defaults are only provided for core plugins and the most commonly used utils like assembly and dependency. Other plugins are not locked and thus you are still subject to picking up new ones as they come out. -----Original Message----- From: Borut Bolčina [mailto:[email protected]] Sent: Wednesday, December 17, 2008 5:49 AM To: Maven Users List Subject: Re: [2.0.10 RC6] please test Hello, I don't know if this was discussed before - why does super pom have plugins which are betas and even alphas? Why are not versions of the plugins consolidated to "solid" versions for each release of Maven? I know the quality of some alpha product may be even better then some not-beta or non-alpha, but the process of releasing new Maven version should include checking and consolidating version numbers/quality of the plugins it fixes in super pom. Do you agree? Regards, Borut 2008/12/17 Brian E. Fox <[email protected]> > Hello, > Thanks everyone for sticking with us this far. I have high hopes of this > being the last RC. > > This RC fixes MNG-3898 and updates the default plugin versions in the > super pom. You can see the changes to the super pom and specific > versions used here: > http://svn.apache.org/viewvc/maven/components/branches/maven-2.0.10-RC/m > aven-project/src/main/resources/org/apache/maven/project/pom-4.0.0.xml?r > 1=708789&r2=726765&diff_format=h<http://svn.apache.org/viewvc/maven/components/branches/maven-2.0.10-RC/maven-project/src/main/resources/org/apache/maven/project/pom-4.0.0.xml?r1=708789&r2=726765&diff_format=h> > > Here's the list of issues fixed in 2.0.10 (updated to remove the wagon > fixes that were rolled back): > > http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14112&styleName > =Html&projectId=10500&Create=Create<http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14112&styleName=Html&projectId=10500&Create=Create> > > And I've staged RC-6 here: > > http://people.apache.org/~brianf/staging-repository/org/apache/maven/apa<http://people.apache.org/%7Ebrianf/staging-repository/org/apache/maven/apa> > che-maven/2.0.10-RC6/ > > > > Please try it out and see if we have any remaining regressions over > 2.0.9. > > Thanks, > Brian > > > ---------------------- > Brian Fox > Apache Maven PMC > http://blogs.sonatype.com/brian/ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
