>Good point, but shouldn't that stable functionality be in the >previous release, which folks should still be using in production >until they need to upgrade?
In this case, yes because the stable goals have not changed at all (and this is where pluginMgt comes in). However if the repos are split, the fact that the plugin as a whole is alpha means it's not easily accessible to someone without adding a pluginRepo to their pom/settings. Meaning that someone can't just type dependency:analyze until it's finally released as 2.0. > You can actually do this (yet another not well documented thing): >mvn org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4:analyze Good to know..this is grotesque, but still easier than changing my "super" pom, redeploying and updating tlp poms etc just to try something out ;-) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
