[
https://issues.apache.org/jira/browse/MNG-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15980534#comment-15980534
]
Ben Caradoc-Davies commented on MNG-5883:
-----------------------------------------
MNG-5185 and MNG-5181 are in the Issue Links section above. The core problem is
that the new repository behaviour is stateful: it remembers the repository of
origin of an artifact. I know this is by design; the consequences of this
decision are noted in this issue and in the two linked issues. It is not the
end of the world, but any solution that requires direct modification of a Maven
repository using {{find}} and {{rm}} is an indication that something is wrong
with the Maven implementation.
> Silence unnecessary legacy local repository warning
> ---------------------------------------------------
>
> Key: MNG-5883
> URL: https://issues.apache.org/jira/browse/MNG-5883
> Project: Maven
> Issue Type: Improvement
> Components: Command Line
> Affects Versions: 3.2.5, 3.3.3, 3.5.0
> Reporter: Ben Caradoc-Davies
> Assignee: Christian Schulte
> Priority: Trivial
>
> 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:
> {code}
> find ~/.m2/repository -name "_*.repositories" -exec rm -f {} \;
> {code}
> Given that users of -llr have made an informed choice to do so, please remove
> the (in my view unnecessary) warning that it generates:
> {code}
> [WARNING] Disabling enhanced local repository: using legacy is strongly
> discouraged to ensure build reproducibility.
> {code}
> Kind regards,
> Ben.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
