Hi Stuart !
Thx for your response...
I've tried to use your suggestion but it does not work for every
artifacts. For example:
when I use:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>RELEASE</version>
<configuration>
...
</configuration>
</plugin>
Maven tries to download version 2.0-beta-5-SNAPSHOT
"org.apache.maven.plugins:maven-release-plugin:pom:2.0-beta-5-20070426.100207-13"
I don't know if it's relevant but I'm using a Maven 2 enterprise
repository (artifactory).
Regards,
Rodrigo.
Stuart McCulloch wrote:
On 30/07/07, Rodrigo Gonçalves <[EMAIL PROTECTED]> wrote:
Hi...
In my poms I have some plugins configured without the version in order
to use the latest one, but in my settings.xml file I need to have some
snapshot-repositories.
So in the builds maven will use the latest version available witch is a
snapshot version, and that is not my intension.
Is there any way to specify maven to use the latest non-snapshot version
of a dependency?
have you tried using a meta-version, such as:
<version>RELEASE</version>
that shouldn't match against any snapshots.
Thx in advance...
Rodrigo.
---------------------------------------------------------------------
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]
