Extremely easy fix for that: http://maven.apache.org/guides/introduction/introduction-to-plugin-resoluti on.html
-- snip -- For clarity, the following are the three ways to reference a mojo from the command line. These will all result in the clean mojo of the maven-clean-plugin being invoked: mvn org.apache.maven.plugins:maven-clean-plugin:2.0:clean mvn org.apache.maven.plugins:maven-clean-plugin:clean mvn clean:clean -- /snip -- So just reference your snapshot plugin with: mvn <groupId>:<artifactId>:<yourVersionIncluding-SNAPSHOT>:<goal> That's it. On 9/27/12 10:35 AM, "Dan Tran" <[email protected]> wrote: >Hello > >Back in Maven 2, when executing a plugin goal from command line, >Maven always tries to look for latest version and its snapshot > >In Maven 3, this capability disappear, Maven only looks for latest >released version. > >Would it possible to turn it on from command line? > >I fully understand the benefit of predictability. However, it becomes >very inconvenient to cut the plugin release while still testing. >and we cannt use maven2 because the plugin itself uses maven 3 api ( ie >aether ) > >Is there already a request for this? > >Big thanks > >-D > >--------------------------------------------------------------------- >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]
