You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "Sebb (JIRA)" <ji...@apache.org> on 2012/10/05 01:35:47 UTC

[jira] [Comment Edited] (IO-125) wrong groupId value in pom.xml

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

Sebb edited comment on IO-125 at 10/5/12 10:35 AM:
---------------------------------------------------

This issue is closed.

Please raise a new JIRA for the Maven deployment problem.
                
      was (Author: sebb@apache.org):
    There are two issues here:
1) what groupId should Commons IO use;
2) how to resolve the conflicting entries in the Maven repo caused by incorrect deployment.

In the case of 1), Commons do not propose to change groupId unless and until it becomes necessary to break binary compatibility. At which point the groupId and package name will both be changed.

Issue 2) is completely different; please raise a separate JIRA.
                  
> wrong groupId value in pom.xml
> ------------------------------
>
>                 Key: IO-125
>                 URL: https://issues.apache.org/jira/browse/IO-125
>             Project: Commons IO
>          Issue Type: Bug
>            Reporter: Piotr Czerwinski
>
> groupId for the project is set to commons-io. I believe it should be org.apache.commons.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira