[
https://issues.apache.org/jira/browse/MNG-7713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17695009#comment-17695009
]
ASF GitHub Bot commented on MNG-7713:
-------------------------------------
slawekjaranowski commented on code in PR #1021:
URL: https://github.com/apache/maven/pull/1021#discussion_r1121551376
##########
maven-embedder/src/main/java/org/apache/maven/cli/CLIManager.java:
##########
@@ -280,6 +280,12 @@ public CLIManager() {
.desc("Ineffective, only kept for backward compatibility")
.build());
+ // Adding this back to make Maven fail if used
Review Comment:
Please add info about conflict with `-l lr` - why we need it
> 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: 4.0.0, 4.0.0-alpha-5, 3.9.1
>
>
> 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)
