[
https://issues.apache.org/jira/browse/VALIDATOR-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13040333#comment-13040333
]
Nick Burch commented on VALIDATOR-253:
--------------------------------------
Backed out in r1128398, as Sebb has pointed out that alas Maven won't do the
right thing for this case:
{quote}
Redirect POMs only work if there is a dependency on that particular
version, and Maven Central does not allow previous versions to be
updated to add redirect POMs. Even if it did, it would take some while
for local workspaces to retrieve the new details.
If an application depends on Validation 1.3 and Validation 1.4 (via
different transitive dependencies) then it will get copies of both
versions.
The only safe solution is to change the package name as well.
Or don''t fix the groupId until you have to change the package name
for some other reason, e.g. API breakage.
{quote}
> Change groupId to org.apache.commons
> ------------------------------------
>
> Key: VALIDATOR-253
> URL: https://issues.apache.org/jira/browse/VALIDATOR-253
> Project: Commons Validator
> Issue Type: Task
> Reporter: Paul Benedict
> Assignee: Nick Burch
> Fix For: 1.4
>
>
> Some existing Commons projects have made the POM move to org.apache.commons
> with their new releases.
> http://repo.mergere.com/maven2/org/apache/commons/
> I think a 1.4 release is a good time to change the groupId as well.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
