[jira] Commented: (MNG-1908) snapshots not deployed using m2, or deployed with uniqueVersion = false are not updated if present locally
[ http://jira.codehaus.org/browse/MNG-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89039 ] Brett Porter commented on MNG-1908: --- Jason, I have test cases in the integration tests showing this works, and they run in every environment I have ever run them in. Do you have: - an additional test case that shows it doesn't work, or - an environment where the test cases fail? If not, I'd prefer to leave this closed for 2.0.5 and open new issues for any new issues found with the functionality. > 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: Jason van Zyl >Priority: Blocker > Fix For: 2.0.6 > > 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
[jira] Commented: (MNG-1908) snapshots not deployed using m2, or deployed with uniqueVersion = false are not updated if present locally
[ 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
[jira] Commented: (MNG-1908) snapshots not deployed using m2, or deployed with uniqueVersion = false are not updated if present locally
[ 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
[jira] Commented: (MNG-1908) snapshots not deployed using m2, or deployed with uniqueVersion = false are not updated if present locally
[ http://jira.codehaus.org/browse/MNG-1908?page=comments#action_78795 ] Tom Spengler commented on MNG-1908: --- 2.1 is realy to late for us, we (100 persons) cannot every day update there local repository with more than 300 artifacts per hand we need a solution nearly today!! > 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.1 > > 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
[jira] Commented: (MNG-1908) snapshots not deployed using m2, or deployed with uniqueVersion = false are not updated if present locally
[ http://jira.codehaus.org/browse/MNG-1908?page=comments#action_75302 ] Adam Lewis commented on MNG-1908: - I have a similar problem. The artifacts are deployed using m2, the metadata on the repo is generated. When I do a build, maven logs that it has found a snapshot version and is checking for updates. It downloads and updates my local metadata for that repo, but DOES NOT download the updated JAR. THIS IS A BLOCKING ISSUE. If a release is not planned soon, the fix needs to be back ported. Having snapshots that don't update reduces the usefullness of SNAPSHOT to ZERO. Actually its worse than that, because we expect that SNAPSHOTS be updated from our internal repo and maven behaves as if it is updating them and then it does NOTHING. A fix in 2.1 does nothing for us if 2.1 doesn't get releases soon. > 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.1 > > 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
[jira] Commented: (MNG-1908) snapshots not deployed using m2, or deployed with uniqueVersion = false are not updated if present locally
[ http://jira.codehaus.org/browse/MNG-1908?page=comments#action_68473 ] Claus M. Vagner commented on MNG-1908: -- Can I please get an update on this issue... I have ran into the problem with maven not updating the snapshot locally if present. The snapshot release is not generated with maven but uploaded manually. Will this be fixed no earlier then 2.1? > 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 > Type: Bug > Components: Artifacts and Repositories > Versions: 2.0.1 > Reporter: Guillaume Nodet > Assignee: Brett Porter > Priority: Blocker > Fix For: 2.1 > > Original Estimate: 30 minutes >Time Spent: 2 hours, 30 minutes > Remaining: 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
