[
http://jira.codehaus.org/browse/MNG-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_88285
]
Jay Kirby commented on MNG-1908:
--------------------------------
Finally got this to work by packaging and deploying using m2 after the m1 build
completed. It only seems to work if the artifacts in the remote repository
have unique names (i.e. with the timestamp in it). You then end up with two
copies of the artifact in the local repo, one with the unique name (i.e.
myartifactid-1.0-20070222.002933-1.jar) and one with the abbreviated
artifactid-versionid name (i.e. myartifact-1.0-SNAPSHOT.jar). Kind of a waste
of space, but at least it works...
> 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
