hi Jörg The problem here is I run my plugin from command line, no pom.
-D On Thu, Sep 27, 2012 at 9:53 AM, Jörg Schaible <[email protected]> wrote: > Hi Dan, > > Dan Tran 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? > > AFAICS this has nothing to do with M2/M3, but early M2 versions simply did > not pin-point the versions of the plugins they used. For latest releases of > M2 (and IIRC all releases of M3) this policy have changed, and you will have > to declare the version of a plugin explicitly in your POMs, if you want to > use a different version than the one that is declared internally. > > - Jörg > > > --------------------------------------------------------------------- > 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]
