You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Vincent Massol <vm...@pivolis.com> on 2005/09/03 21:54:18 UTC
Problem with surefire plugin's version
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)?
Thanks
-Vincent
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Problem with surefire plugin's version
Posted by Brett Porter <br...@apache.org>.
The flag is for use when you install the surefire plugin.
- Brett
Vincent Massol wrote:
>
>
>>-----Original Message-----
>>From: Brett Porter [mailto:brett@apache.org]
>>Sent: dimanche 4 septembre 2005 09:05
>>To: Maven Developers List
>>Subject: Re: Problem with surefire plugin's version
>>
>>Are you sure? This is exactly what the bootstrap does to ensure all the
>>latest plugins are used that it just built.
>>
>>
>
>I'm pretty sure:
>
>C:\dev\cargo\samples\java>m2 -DupdateReleaseInfo=true install
>[...]
> [INFO] maven-surefire-plugin: resolved to version 2.0-alpha-3 from local
>repository
>[...]
>
>And if I look into my m2 repo:
>
>C:\Documents and Settings\Vincent
>Massol\.m2\repository\org\apache\maven\plugins\maven-surefire-plugin>dir
> Volume in drive C has no label.
> Volume Serial Number is 9445-8590
>
> Directory of C:\Documents and Settings\Vincent
>Massol\.m2\repository\org\apache\maven\plugins\maven-surefire-plugin
>
>03/09/2005 11:58 <DIR> .
>03/09/2005 11:58 <DIR> ..
>04/09/2005 08:51 <DIR> 2.0-alpha-3
>30/08/2005 18:11 <DIR> 2.0-beta-1-SNAPSHOT
>03/09/2005 11:58 19 maven-surefire-plugin-LATEST.version.txt
>04/09/2005 08:50 11
>maven-surefire-plugin-RELEASE.version.txt
> 2 File(s) 30 bytes
> 4 Dir(s) 14 074 413 056 bytes free
>
>Inside the LATEST file, it says: 2.0-beta-1-SNAPSHOT
>And inside the RELEASE one: 2.0-alpha-3
>
>If I delete those files they get recreated with the same content.
>
>Thanks
>-Vincent
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Problem with surefire plugin's version
Posted by "Johnny R. Ruiz " <jr...@exist.com>.
Vincent,
I had this problem before, as far as I can remember i resolved this
problem by deleting "maven-surefire-plugin-LATEST.version.txt" and the
file "pluginRegistry.xml" in ".m2" directory in my local repo. Try it out.
Johnny
Vincent Massol wrote:
>
>
>>-----Original Message-----
>>From: Brett Porter [mailto:brett@apache.org]
>>Sent: dimanche 4 septembre 2005 09:05
>>To: Maven Developers List
>>Subject: Re: Problem with surefire plugin's version
>>
>>Are you sure? This is exactly what the bootstrap does to ensure all the
>>latest plugins are used that it just built.
>>
>>
>
>I'm pretty sure:
>
>C:\dev\cargo\samples\java>m2 -DupdateReleaseInfo=true install
>[...]
> [INFO] maven-surefire-plugin: resolved to version 2.0-alpha-3 from local
>repository
>[...]
>
>And if I look into my m2 repo:
>
>C:\Documents and Settings\Vincent
>Massol\.m2\repository\org\apache\maven\plugins\maven-surefire-plugin>dir
> Volume in drive C has no label.
> Volume Serial Number is 9445-8590
>
> Directory of C:\Documents and Settings\Vincent
>Massol\.m2\repository\org\apache\maven\plugins\maven-surefire-plugin
>
>03/09/2005 11:58 <DIR> .
>03/09/2005 11:58 <DIR> ..
>04/09/2005 08:51 <DIR> 2.0-alpha-3
>30/08/2005 18:11 <DIR> 2.0-beta-1-SNAPSHOT
>03/09/2005 11:58 19 maven-surefire-plugin-LATEST.version.txt
>04/09/2005 08:50 11
>maven-surefire-plugin-RELEASE.version.txt
> 2 File(s) 30 bytes
> 4 Dir(s) 14 074 413 056 bytes free
>
>Inside the LATEST file, it says: 2.0-beta-1-SNAPSHOT
>And inside the RELEASE one: 2.0-alpha-3
>
>If I delete those files they get recreated with the same content.
>
>Thanks
>-Vincent
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Problem with surefire plugin's version
Posted by Vincent Massol <vm...@pivolis.com>.
> -----Original Message-----
> From: Brett Porter [mailto:brett@apache.org]
> Sent: dimanche 4 septembre 2005 09:05
> To: Maven Developers List
> Subject: Re: Problem with surefire plugin's version
>
> Are you sure? This is exactly what the bootstrap does to ensure all the
> latest plugins are used that it just built.
I'm pretty sure:
C:\dev\cargo\samples\java>m2 -DupdateReleaseInfo=true install
[...]
[INFO] maven-surefire-plugin: resolved to version 2.0-alpha-3 from local
repository
[...]
And if I look into my m2 repo:
C:\Documents and Settings\Vincent
Massol\.m2\repository\org\apache\maven\plugins\maven-surefire-plugin>dir
Volume in drive C has no label.
Volume Serial Number is 9445-8590
Directory of C:\Documents and Settings\Vincent
Massol\.m2\repository\org\apache\maven\plugins\maven-surefire-plugin
03/09/2005 11:58 <DIR> .
03/09/2005 11:58 <DIR> ..
04/09/2005 08:51 <DIR> 2.0-alpha-3
30/08/2005 18:11 <DIR> 2.0-beta-1-SNAPSHOT
03/09/2005 11:58 19 maven-surefire-plugin-LATEST.version.txt
04/09/2005 08:50 11
maven-surefire-plugin-RELEASE.version.txt
2 File(s) 30 bytes
4 Dir(s) 14 074 413 056 bytes free
Inside the LATEST file, it says: 2.0-beta-1-SNAPSHOT
And inside the RELEASE one: 2.0-alpha-3
If I delete those files they get recreated with the same content.
Thanks
-Vincent
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Problem with surefire plugin's version
Posted by Brett Porter <br...@apache.org>.
Are you sure? This is exactly what the bootstrap does to ensure all the
latest plugins are used that it just built.
- Brett
Vincent Massol wrote:
>>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.
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Problem with surefire plugin's version
Posted by Vincent Massol <vm...@pivolis.com>.
> -----Original Message-----
> From: Vincent Massol [mailto:vmassol@pivolis.com]
> Sent: dimanche 4 septembre 2005 08:53
> To: 'Maven Developers List'
> Subject: RE: Problem with surefire plugin's version
[snip]
> > 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.
s/also/always.
-Vincent
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Problem with surefire plugin's version
Posted by Vincent Massol <vm...@pivolis.com>.
> -----Original Message-----
> From: Brett Porter [mailto:brett@apache.org]
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Problem with surefire plugin's version
Posted by Brett Porter <br...@apache.org>.
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.
- Brett
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)?
>
>Thanks
>-Vincent
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org