This wiki refers to Maven 2 clients having problems accessing Maven 3 artifacts. In my
situation Maven 3 clients are the problem; they does not seem to find the artifacts it
deployed itself. So that would not be "activating legacy behavior".
On 27-10-2010 14:47, Benjamin Bentmann wrote:
Tom wrote:
Could not
find artifact nl.innovationinvestments:CheyenneServlet:jar:1.11-SNAPSHOT
in kp (http://alaya.applicationplaza.com:8081/nexus/content/groups/pub
lic)
Could be related to [0], i.e. a problem with the metadata that Maven requires
to locate the timestamped snapshot. Either try using the system property
mentioned in the wiki article to deploy legacy metadata or update/patch your
Nexus instance.
Benjamin
[0]
https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes#Maven3.xCompatibilityNotes-UniqueSnapshotVersionsandClassifiers
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
