[ https://issues.apache.org/jira/browse/MNG-7713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17695003#comment-17695003 ]
ASF GitHub Bot commented on MNG-7713: ------------------------------------- cstamas opened a new pull request, #1021: URL: https://github.com/apache/maven/pull/1021 As with previous PR (simple removal) the `-llr` got interpreted as `-l lr`, it logged all output to `lr` file. This would maean that use of `-llr` would still sneakily 'work' and probably cause surprise down the road to users. Returned the option, and expicitly checking for it's presence to be able to fail with meaningful message. --- https://issues.apache.org/jira/browse/MNG-7713 > 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)