[
https://issues.apache.org/jira/browse/MNG-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215947#comment-17215947
]
Michael Osipov commented on MNG-5883:
-------------------------------------
The issue is about silencing the warning and not the suboptimal local
repository manager. Please go ahead and create an issue about a new/better/more
roaming savvy approach for Maven 4. Note that the issue is not really related
to Maven, but is completely in Maven Resolver. In theory this could come
earlier.
I believe that the enhanced approach was desinged w/o repository managers in
mind. From my understanding, when using a mirror on a repository manager with a
proxy group you never know from which original repo the artifact came. The
mirror must respond with the original (source) repo id to Resolver to be
written down in the {{_remote.properties}}. Naturally, this can only apply to
publically available repos when you are working from home, but with this it
should solve the most problems people have reported. If you originator id
proves to be correct, this would take a long time to coordinate with all major
repo manager providers to integrate.
> 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
> 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
(v8.3.4#803005)
