[
http://jira.codehaus.org/browse/MNG-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_88156
]
Jay Kirby commented on MNG-1908:
--------------------------------
This is still an issue in 2.0.5. I can never get an artifact with a non-unique
version number containing SNAPSHOT to update in the local repository. I get a
message like:
[DEBUG] repository metadata for: 'snapshot mygroup:myartifact:main-SNAPSHOT'
could not be found on repository: devst
even though it appears as though the correct metadata is present on the remote
server. A new maven-metadata-devst.xml is created in the local repository, but
none of the artifacts are pulled.
How do I reopen this?
> snapshots not deployed using m2, or deployed with uniqueVersion = false are
> not updated if present locally
> ----------------------------------------------------------------------------------------------------------
>
> Key: MNG-1908
> URL: http://jira.codehaus.org/browse/MNG-1908
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.1
> Reporter: Guillaume Nodet
> Assigned To: Brett Porter
> Priority: Blocker
> Fix For: 2.0.5
>
> Original Estimate: 30 minutes
> Time Spent: 2 hours, 30 minutes
> Remaining Estimate: 0 minutes
>
> It seems from the log info that m2 is trying to locate the artifact metadata
> on the repository.
> SInce this artifact has been generated from m1, there is no metadata.
> So whatever repository settings are configured, m2 will never update snapsots.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
