![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
1.2 |
|
Assignee:
|
Unassigned |
|
Created:
|
17/May/13 3:46 AM
|
|
Description:
|
In the pom.xml of my project I have a SNAPSHOT parent.
With maven2 when running versions:update-parent I get:
[INFO] Updating parent from 1.0.24-SNAPSHOT to 1.0.23
(that's the behaviour I expect)
With maven3 I get:
[WARNING] Not updating version: could not resolve any versions
The version 1.0.24-SNAPSHOT is in a "snapshot" repository enabled only for snapshots, and the version 1.0.23 is in an "internal" repository enabled only for releases.
It seems that maven3 looks for newer versions only in the "snapshot" repository...
From what I can see in the logs:
[DEBUG] Skipping update check for artifact myGroup:myParent (<home>/.m2/repository/myGroup/myParent/maven-metadata-internal.xml) from disabled repository internal (http://<repo_url>/archiva/repository/internal)
[DEBUG] Determining update check for artifact myGroup:myParent (<home>/.m2/repository/myGroup/myParent/maven-metadata-snapshot.xml) from snapshot (http://<repo_url>/archiva/repository/snapshots)
...
[DEBUG] Proposal is to update from 1.0.24-SNAPSHOT to null
|
|
Project:
|
Maven 2.x Versions Plugin
|
|
Priority:
|
![Critical]() Critical
|
|
Reporter:
|
Amélie Deltour
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
