I've contemplated this myself recently given that 1.1 is not moving along as fast as I'd hoped. My main concern was confusion with yet another release, and that because uptake is often quite slow on minor revisions it would not be picked up before 1.1 was out anyway.
I'm interested to hear what others think. - Brett Henning P. Schmiedehausen wrote: >Hi, > >due to some questions related to plugin changes on another mailing >list, I wondered what changes have been done to the maven-1.0 branch >(http://svn.apache.org/repos/asf/maven/maven-1/core/branches/MAVEN-1_0-BRANCH) >post the maven-1.0.2 release >(http://svn.apache.org/repos/asf/maven/maven-1/core/tags/MAVEN_1_0_2). > >A diff came up with "no changes". > >As maven 1.0.x has proven to be stable, there are many users out >there that probably cannot upgrade to a beta version and are forced to >use a maven 1.0 version for building. > >The 1.0.2 release is now ~nine months old and a number of plugins >included with 1.0.2 have been significantly upgraded (e.g. Subversion >support in Changelog or the xdoc plugin (which still shows 1.9 on the >download page BTW) or the jar/artifact deploy code (which even uses a >different syntax for describing the upload repositories now). > >So, wouldn't it make sense to cut a maven 1.0.3 release with the core >unchanged and just the upgraded plugins bundled? This would also bring >the 1.0.x plugins more in line with the documentation on the web site. > >(e.g. if you download maven 1.0.2, you get maven-jar-plugin 1.6.1. The >docs on the web site are for 1.7 and simply not working for >1.6.1. There is not documentation for maven-jar-plugin anywhere to >find on the maven web site (or I was not able to find it)). > > Best regards > Henning > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
