jira-importer commented on issue #140: URL: https://github.com/apache/maven-deploy-plugin/issues/140#issuecomment-2771509881
**[Herve Boutemy](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hboutemy)** commented I understand your arguments. IMHO, users who did not migrate are precisely those who won't be able to lock the plugin version: they'll say that "Maven doesn't work", and we'll have to convince them that not specifying plugin version was a bad habit... On the other hand, having these XML encoding support classes copied in 4 components is not so hard for me to maintain: 1 line change in 6 months. And I don't think there will be more change in next months. MSITE-242 has more sources copied (cli, interpolation and introspection): perhaps these classes are more like a problem. Really, now that the compromise is tracked in these 4 Jira issues to be sure it's not forgotten, I think we don't need to hurry: time is our friend. Personally, I don't think changing prerequisite is a good idea before next release of install, deploy and release plugins since last releases are a bit old. For each plugin, when the next release is out, perhaps it will be the good time to look at this issue. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
