commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (VALIDATOR-253) Change groupId to org.apache.commons
Date Fri, 27 May 2011 17:09:47 GMT

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

Sebb commented on VALIDATOR-253:
--------------------------------

Unfortunately redirect POMs don't provide a full solution, unless they can be deployed for
all existing releases.

This is not allowed by Maven Central; anyway, even if it were, there would be local workspaces
with out-of-date POMs.

Any change of Maven groupId/artifactId must be accompanied by change of package name to avoid
problems with multiple jars on the same classpath.

> 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

Mime
View raw message