[jira] [Closed] (MNG-5883) Silence unnecessary legacy local repository warning

["Michael Osipov (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MNG-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MNG-5883.
-------------------------------
    Resolution: Won't Fix

I have read through all comments and related tickets. Many of the comments are offtopic and do not relate to the issue itself. Silencing or removing the message does not solve the problem, but only the cause. We surely need to review the local repository approach for Maven 4.x.

> 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)