[
https://issues.apache.org/jira/browse/MNG-8409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17903762#comment-17903762
]
Tamas Cservenak commented on MNG-8409:
--------------------------------------
Its not first or last, it's all or nothing. Maven3 allowed you to have
stale/unusable passwords and produced weird messages (later on) when the
password was to be used. Maven4 wants to decode (and to succeed in doing so)
all of your passwords, so it is all or nothing. Even if one fails (as you have
one stale pw in settings), it will back out, as it may later on produce weird
situation, misleading errors messages, and so on. So, for simplicity sake,
Maven4 will not let you continue as long you have one legacy or modern pw that
cannot be decoded.
> No upgrade path for settings-security.xml
> -----------------------------------------
>
> Key: MNG-8409
> URL: https://issues.apache.org/jira/browse/MNG-8409
> Project: Maven
> Issue Type: Bug
> Affects Versions: 4.0.0-beta-5, 4.0.0-rc-1
> Reporter: Lenny Primak
> Priority: Blocker
>
> There is no upgrade path to mvnenc from current settings-security.xml
> Everything is failing if settings.xml has maven 3-type passwords.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
