[jira] Reopened: (MNG-1908) snapshots not deployed using m2, or deployed with uniqueVersion = false are not updated if present locally

2007-03-02 Thread Jason van Zyl (JIRA)

 [ 
http://jira.codehaus.org/browse/MNG-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason van Zyl reopened MNG-1908:


  Assignee: Jason van Zyl  (was: Brett Porter)

This does not appear to be fixed and is related to MNG-2289.

 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] Reopened: (MNG-1908) snapshots not deployed using m2, or deployed with uniqueVersion = false are not updated if present locally

2007-01-03 Thread Brett Porter (JIRA)
 [ http://jira.codehaus.org/browse/MNG-1908?page=all ]

Brett Porter reopened MNG-1908:
---

 
the current fix has resulted in a regression in the release update 
functionality. Another IT is in order.

 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] Reopened: (MNG-1908) snapshots not deployed using m2, or deployed with uniqueVersion = false are not updated if present locally

2006-03-15 Thread Brett Porter (JIRA)
 [ http://jira.codehaus.org/browse/MNG-1908?page=all ]
 
Brett Porter reopened MNG-1908:
---


need to investigate the performance regression caused by these revisions

 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: Critical
  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