You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2023/04/06 18:29:00 UTC

[jira] [Commented] (MNG-7713) Drop option legacy-local-repository

    [ https://issues.apache.org/jira/browse/MNG-7713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17709475#comment-17709475 ] 

ASF GitHub Bot commented on MNG-7713:
-------------------------------------

anatolVasin commented on PR #1018:
URL: https://github.com/apache/maven/pull/1018#issuecomment-1499458903

   > resolver option
   
   Hello @cstamas , could you clarify what particular resolver option do you mean? Thanks.
   Such capabilities really requires for emulate closed environments without access to Maven Central in tests.




> Drop option legacy-local-repository
> -----------------------------------
>
>                 Key: MNG-7713
>                 URL: https://issues.apache.org/jira/browse/MNG-7713
>             Project: Maven
>          Issue Type: Task
>          Components: Core
>            Reporter: Tamas Cservenak
>            Assignee: Tamas Cservenak
>            Priority: Major
>             Fix For: 3.9.1, 4.0.0-alpha-5, 4.0.0
>
>
> The option offers several ways to make Maven 3 use Maven 2 legacy local repository, the option help text states: "Use Maven 2 Legacy Local Repository behaviour, ie no use of _remote.repositories. Can also be activated by using -Dmaven.legacyLocalRepo=true".
> Let's drop this option, as there is no need to make Maven 3.9 support Maven 2 local repository, that is (should be) transient anyway. Also, if really needed, there IS a resolver configuration that offers somewhat similar semantics, but Maven CLI should NOT advertise Maven 2 backward compatibility anymore.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)