[
http://jira.codehaus.org/browse/MDEPLOY-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_119700
]
Herve Boutemy commented on MDEPLOY-70:
--------------------------------------
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.
> remove copy of plexus-utils' XML encoding support sources
> ---------------------------------------------------------
>
> Key: MDEPLOY-70
> URL: http://jira.codehaus.org/browse/MDEPLOY-70
> Project: Maven 2.x Deploy Plugin
> Issue Type: Task
> Affects Versions: 2.4
> Reporter: Herve Boutemy
> Priority: Minor
>
> need to upgrade prerequisite to Maven 2.0.6
> see http://docs.codehaus.org/display/MAVENUSER/XML+encoding
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
