Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Critical
-
Resolution: Incomplete
-
Affects Version/s: 2.0.7
-
Fix Version/s: None
-
Component/s: Artifacts and Repositories
-
Labels:None
Description
The particular scenario here is
1.) Deploy snapshot using uniqueVersion false in distribution management
2.) Verify repository has latest snapshot and metadata is updated in build number and timestamp
3. ) Goto a developer's machine (not the same as from which it was deployed) and do mvn -U or specify updates to be always in pom
4.) Local cache shows the maven metadata xml file is updated but the snapshot artifact (jar in this case) is not
Issue Links
- relates to
-
MNG-1908
snapshots not deployed using m2, or deployed with uniqueVersion = false are not updated if present locally
-
why does the metadata have a buildnumber and timestamp if uniqueVersion is false?
mixing the two types of deployments will certainly cause problems.