> -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: dimanche 4 septembre 2005 02:26 > To: Maven Developers List > Subject: Re: Problem with surefire plugin's version > > It uses the latest release. The most reliable way right now (only > required once): > > m2 -DupdateReleaseInfo=true install > > If you still have issues, check ~/.m2/plugin-registry.xml remove a > forced version. > > This area still needs a lot of polish.
I should have been clearer in my email. I've tried all this but m2 also thinks that the latest version is the 2.0 alpha 3 one and not the beta 1. Thanks -Vincent > Vincent Massol wrote: > > >Does anyone know how I can force m2 to use a plugin I've just built? > > > >More precisely, my m2 install always picks version 2.0 alpha 3 of the > >surefire plugin whereas I have a more recent version (2.0 beta 1). I've > >tried removing the metadata files but still m2 always pick the alpha 3 > >version. > > > >How does it pick one over the other (what strategy m2 is using)? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
