You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tamas Cservenak (Jira)" <ji...@apache.org> on 2023/03/01 07:31:00 UTC
[jira] [Updated] (MNG-7713) Drop option legacy-local-repository
[ https://issues.apache.org/jira/browse/MNG-7713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tamas Cservenak updated MNG-7713:
---------------------------------
Fix Version/s: 4.0.0
4.0.0-alpha-5
> 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-candidate, 4.0.0, 4.0.0-alpha-5
>
>
> 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)