Not to be a party pooper but given all the discussions that are cropping up over and around this release, I feel like a vote of -1 is in order.
On Wed, Mar 19, 2008 at 11:42 AM, Brian E. Fox <[EMAIL PROTECTED]> wrote: > >Well, the auto-update of the archetype-plugin certainly has caused a > LOT > >of issues lately. Would that be considered one of your "commonly used > > >utilities"? > > Normally yes, but it's already out there and locking down to alpha-2 > probably isn't a good idea as it will block lots of people from getting > the later alphas. Once it's out of alpha/beta then yes we should lock > it. > > Here's my initial thought process: Only lock down default plugins and > some utils like assembly, dependency etc. These should be locked to the > current latest version so that anyone using 2.0.8 that hasn't already > locked them down (which should still be best practice) doesn't get > downgraded. > > Later on, we should not lock down to anything but a full release unless > there is significant cause to do otherwise. Also, I think we should not > lock down to anything that has been released less than 30 days again > unless there is a good reason. We don't want to find out about > regressions by locking down on a new version. > > -----Original Message----- > From: Daniel Kulp [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 19, 2008 11:33 AM > To: dev@maven.apache.org > Cc: Brian E. Fox > Subject: Re: [Pre-Vote] release maven 2.0.9 > > > Well, the auto-update of the archetype-plugin certainly has caused a LOT > > of issues lately. Would that be considered one of your "commonly used > utilities"? > > Dan > > On Wednesday 19 March 2008, Brian E. Fox wrote: > > Crap. I'll have to fix the ear version. The other stuff I don't think > > needs to be locked down. The goal was to lock down the most important > > plugins, things that directly affect a build as part of the default > > lifecycle and commonly used utilities. I don't think we want to start > > including every single plugin in here, it was never the intent. > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > > Behalf Of nicolas de loof > > Sent: Wednesday, March 19, 2008 11:18 AM > > To: Maven Developers List > > Subject: Re: [Pre-Vote] release maven 2.0.9 > > > > I notice some official maven plugin don't have fixed version in the > > super-POM : > > > > maven-archetype-plugin > > maven-checkstyle-plugin > > maven-eclipse-plugin > > maven-idea-plugin > > maven-jxr-plugin > > maven-invoker-plugin > > maven-one-plugin > > maven-patch-plugin > > maven-pmd-plugin > > maven-projecthelp-plugin > > maven-remote-resources-plugin > > maven-repository-plugin > > maven-shade-plugin > > maven-scm-plugin > > maven-stage-plugin > > maven-verifier-plugin > > maven-project-info-reports-plugin > > maven-surefire-report-plugin > > > > > > maven-ear-plugin is set a version 2.1, and 2.3.1 is the latest > > available. > > > > Also maven-install-plugin is not right ordered considering alphabetic > > order > > (not an issue but makes this check more difficult) > > > > 2008/3/18, Brian E. Fox <[EMAIL PROTECTED]>: > > > The list of fixes in this release is substantial. See release notes > > > at the bottom. High level changes are: locking down the plugins in > > > the super pom, new import scope, new toolchain support, native > > > webdav support, execution inheritance=false is fixed, plugin > > > dependency overrides, errors in transfer won't corrupt the local > > > repo, and generally a lot of fixes for artifact resolution and other > > > identified regressions from the user list. > > > > > > > > > > > > The release is staged at: > > > > > > http://people.apache.org/~brianf/staging-repository/<http://people.apache.org/%7Ebrianf/staging-repository/> > > > > > > > > > > > > The bundles are here: > > > > http://people.apache.org/~brianf/staging-repository/org/apache/maven/a<http://people.apache.org/%7Ebrianf/staging-repository/org/apache/maven/a> > >pa > > > > > che-maven/2.0.9/ > > > > > > > > > > > > I'll let this staged RC sit for a few days before calling the formal > > > vote. > > > > > > > > > > > > Release Notes - Maven 2 - Version 2.0.9 > > > > > > > > > > > > > > > > > > ** Bug > > > > > > * [MNG-1412] - dependency sorting in classpath > > > > > > * [MNG-1914] - Wrong url in error message when using a mirror > > > > > > * [MNG-2123] - NullPointerException when a dependency uses > > > version range and another uses an actual version incompatible with > > > that range > > > > > > * [MNG-2145] - Plugins' dependencies are not always checked > > > > > > * [MNG-2178] - incorrect M2_HOME guess in mvn.bat > > > > > > * [MNG-2234] - activeProfile in ~/.m2/settings.xml is ignored > > > when profiles section is missing or empty > > > > > > * [MNG-2339] - ${project.*} are interpreted in the wrong place > > > > > > * [MNG-2744] - checksum comparison should be case-insensitive > > > > > > * [MNG-2809] - Can't activate a profile by checking for the > > > > presence > > > > > of a file in ${user.home} > > > > > > * [MNG-2848] - Environment variables in profile activation not > > > working > > > > > > * [MNG-2861] - NullPointerException in DefaultArtifactCollector > > > > for > > > > > relocated resolvedArtifacts with different version ranges and > > > > available > > > > > versions. > > > > > > * [MNG-2925] - NullPointerException in > > > PluginDescriptor.getMojo() > > > > if > > > > > there's no mojo in pom.xml > > > > > > * [MNG-2928] - Null pointer exeception when introducing version > > > range [major.minor.build-SNAPSHOT,) > > > > > > * [MNG-2956] - The documentation refers to system property > > > "user.dir" when it should refer to "user.home" > > > > > > * [MNG-2972] - Ignores version of plugin dependency specified in > > > > my > > > > > pom > > > > > > * [MNG-3086] - NullPointerException in > > > ResolutionNode.getTrail(ResolutionNode.java:136) > > > > > > * [MNG-3099] - Profiles ignored when working with non-projects > > > > (such > > > > > as archetype:create) > > > > > > * [MNG-3111] - Classpath order incorrect > > > > > > * [MNG-3156] - NullPointerException with mvn dependency:sources > > > > > > * [MNG-3221] - Infinite loop in DefaultLifecycleExecutor > > > > > > * [MNG-3259] - Regression: Maven drops dependencies in > > > > multi-module > > > > > build > > > > > > * [MNG-3288] - Invalid systemPath allows build to > > > > continue--failing > > > > > in later phase. > > > > > > * [MNG-3296] - mvn.bat looses error code on windows NT type > > > platforms > > > > > > * [MNG-3310] - JAVACMD set incorrectly when JAVA_HOME is not set > > > > > > * [MNG-3316] - Barfs at attribues named .*encoding > > > > > > * [MNG-3354] - mvn.bat incorrectly detects OS on Windows NT or > > > XP with Novell login > > > > > > * [MNG-3355] - CLONE -${pom.build.sourceDirectory} and > > > ${pom.build.testSourceDirectory} no longer recognized > > > > > > * [MNG-3365] - Remove trailing-backslashes from M2_HOME in > > > mvn.bat > > > > > > * [MNG-3394] - Plugin versions inherited via <pluginManagement> > > > cannot be overriden by <build>.<plugins> section of sub modules > > > > > > * [MNG-3396] - Managed versions dont affect over constrained > > > > ranges > > > > > * [MNG-3400] - MavenProject is not extensible > > > > > > * [MNG-3405] - "Checking for updates from repository" logging > > > > should > > > > > not display if WagonManager is offline > > > > > > * [MNG-3410] - Managed versions in plugins are not considered > > > when using them > > > > > > * [MNG-3415] - Transfer errors cause junk metadata in the local > > > > repo > > > > > * [MNG-3426] - regression : <dependency> in plugin configuration > > > doesn't override plugin classpath > > > > > > * [MNG-3430] - Toolchain doesn't match Toolchain extensions > > > > > > * [MNG-3431] - Pom Extensions not supported for Toolchains > > > > > > * [MNG-3439] - incorrect child dependency selected when parent > > > is not selected > > > > > > * [MNG-3441] - Maven should always retrieve metadata to be > > > updated from the deployment repository > > > > > > * [MNG-3460] - > > > org.apache.maven.profiles.DefaultProfileManagerTest fails if you use > > > a different local repo > > > > > > * [MNG-3464] - maven-toolchains missing from final binary.. need > > > > to > > > > > update the assembly > > > > > > > > > > > > ** Improvement > > > > > > * [MNG-428] - Japanese message resource > > > > > > * [MNG-2881] - Improve logging when downloading snapshots in > > > > offline > > > > > mode > > > > > > * [MNG-3119] - Duplicate attached artifacts should not be > > > allowed. > > > > > > * [MNG-3279] - Support Exception Chaining for > > > MojoFailureException > > > > > > * [MNG-3318] - ActiveProjectArtifact should have appropriate > > > > equals > > > > > and hashCode methods > > > > > > * [MNG-3331] - Normalize paths to sub modules > > > > > > * [MNG-3388] - DefaultPluginManager needs to catch LinkageError > > > > > > * [MNG-3395] - Default core plugin versions in the superpom. > > > > > > * [MNG-3442] - Add explicit resource bundle for English > > > > > > * [MNG-3453] - Avoid references to the deprecated expression > > > "${project.build.resources}" > > > > > > * [MNG-3461] - Mirrors should not apply to file:// repositories > > > > > > > > > > > > ** New Feature > > > > > > * [MNG-2664] - Add native support for webdav > > > > > > * [MNG-3360] - Added the documentation in the Maven release > > > > > > > > > > > > ** Task > > > > > > * [MNG-2883] - Make sure that the network isn't used for > > > snapshots in offline mode when legacy repositories are used > > > > > > > > > > > > > > > > > > ** Wish > > > > > > * [MNG-1491] - Reactor should print out a message if it detects > > > a collision of artifact ids > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > -- > J. Daniel Kulp > Principal Engineer, IONA > [EMAIL PROTECTED] > http://www.dankulp.com/blog > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Justice is nothing more than that which is in the greatest self-interest of the largest portion of the population.
