On 1/18/07, Brett Porter <[EMAIL PROTECTED]> wrote:
you have a very old snapshot of the plugin plugin. 2.2 has been
released.
The questions are:
- why did maven 2.0.5 not use the 2.2-SNAPSHOT plugin that could be
found in my local repository ?
- why did it manage to download 2.2 once I cleaned up my local
repository ? couldn't it download the latest version of the plugin the
first time I ran it on that project ?
I don't understand why maven failed in that case and why removing all
old instances of the plugin in my local repos. made it work again.
Maybe something is missing in my understanding on the way maven
decides to find new plugin versions.
Also, builds should not even be attempting to get snapshots from
http://repository.codehaus.org.
the root mojo pom defines:
<pluginRepositories>
<pluginRepository>
<id>snapshots</id>
<name>Maven Central Development Plugin Repository</name>
<url>http://snapshots.repository.codehaus.org</url>
<releases>
<enabled>false</enabled>
</releases>
</pluginRepository>
<pluginRepository>
<id>codehaus.org</id>
<name>Codehaus Central Plugin Repository</name>
<url>http://repository.codehaus.org</url>
</pluginRepository>
</pluginRepositories>
It looks like
<snapshots>
<enabled>false</enabled>
</snapshots>
is missing for the non snapshot repository...
Jerome
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
