Details
-
Improvement
-
Status: Closed
-
Trivial
-
Resolution: Won't Fix
-
3.2.5, 3.3.3, 3.5.0
-
None
-
None
Description
Having been burned on several occasions by the new local repository behaviour, which in effect scopes artifacts by their origin (when first stored in the local repository), I was delighted by the introduction of the -llr command line option in 3.0.3. I now use this behaviour for all builds to avoid the build instability caused by remote repository migration. This avoids the need to start each build with:
find ~/.m2/repository -name "_*.repositories" -exec rm -f {} \;
Given that users of -llr have made an informed choice to do so, please remove the (in my view unnecessary) warning that it generates:
[WARNING] Disabling enhanced local repository: using legacy is strongly discouraged to ensure build reproducibility.
Kind regards,
Ben.
Attachments
Issue Links
- is related to
-
MNG-5185 Improve "missing dependency" error message when _maven.repositories/_remote.repositories contains other repository ids than requested
- Closed
-
MNG-5181 New resolution from local repository is very confusing
- Closed
- relates to
-
MNG-7001 Reconsider seemingly useless check of artifacts' source repository introduced in Maven 3.0
- Open
- mentioned in
-
Page Loading...