You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Stephen Connolly (JIRA)" <ji...@apache.org> on 2017/02/23 15:01:02 UTC

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

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

Stephen Connolly updated MNG-5883:
----------------------------------
    Fix Version/s: 3.5.0-alpha-2
                   3.5.0-alpha-1

> 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
>            Reporter: Ben Caradoc-Davies
>            Assignee: Christian Schulte
>            Priority: Trivial
>             Fix For: 3.5.0, 3.5.0-alpha-1, 3.5.0-alpha-2
>
>
> 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)