-
Notifications
You must be signed in to change notification settings - Fork 143
Closed
Labels
bugSomething isn't workingSomething isn't workingpriority:blockerBlocks development and/or testing work, production could not runBlocks development and/or testing work, production could not run
Milestone
Description
Tamas Cservenak opened MRESOLVER-373 and commented
The change done in MRESOLVER-346 in relation to DefaultArtifactResolver and DefaultMetadataResolver is wrong as it attempts lock upgrade. Also, is actually complemented by MRESOLVER-349 may not needed. The change happened for DefaultDeployer is correct.
Problem is that now the pair (DefaultArtifactResolver and DefaultMetadata resolver) in case of model building involving snapshot parent POM attempt lock upgrade (unintentionally).
Issue Links:
- MNG-7819 Create IT that exercise file locking with snapshots
("fixes")
Remote Links:
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingpriority:blockerBlocks development and/or testing work, production could not runBlocks development and/or testing work, production could not run