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

Tamas Cservenak commented on MNG-6889:
--------------------------------------

I agree with [~michael-o] here, hopefully others as well:
 * deprecate in 3.8.8
 * drop in 3.9+

I know this is a bit "awkward", as 3.9.0 is already out, but IMHO it is 
important for us to move fast here.

For users requiring this we still can provide alternative (the resolver 
config), but they should be aware that they not only loose artifact provenance, 
but risk their build stability/reproducibility as well, and finally, they will 
MISS all the new things from latest Maven, like split repo etc.

> Mark command line option --legacy-local-repository as deprecated
> ----------------------------------------------------------------
>
>                 Key: MNG-6889
>                 URL: https://issues.apache.org/jira/browse/MNG-6889
>             Project: Maven
>          Issue Type: Task
>          Components: Command Line
>    Affects Versions: 3.6.3
>            Reporter: Karl Heinz Marbaise
>            Assignee: Karl Heinz Marbaise
>            Priority: Minor
>             Fix For: 4.0.x-candidate
>
>
> We should at least mark this option as deprecated or even better remove this 
> option but this would be inconsistent to remove something which has not been 
> marked deprecated before.



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

Reply via email to