commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stevo Slavic (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DBUTILS-92) Align maven groupId with rest of the apache commons projects
Date Sun, 08 Jul 2012 16:46:34 GMT

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

Stevo Slavic commented on DBUTILS-92:
-------------------------------------

Oh, right, that's why commons-lang and similar have added numbers to the package names in
relocated releases.
I think though, unlike commons-lang, that it's much less likely that one would use one variant
of dbutils directly and get the other one transitively.
Nevertheless, to stay on the safe side, probably better to follow the pattern and include
in coordinates change also package change, and do that in a major (2.0) release.
                
> Align maven groupId with rest of the apache commons projects
> ------------------------------------------------------------
>
>                 Key: DBUTILS-92
>                 URL: https://issues.apache.org/jira/browse/DBUTILS-92
>             Project: Commons DbUtils
>          Issue Type: Improvement
>    Affects Versions: 1.4
>            Reporter: Stevo Slavic
>         Attachments: DBUTILS-92.patch, pom.xml
>
>
> It seems to be the trend (maybe there's even some convention/agreement among Apache Commons
developers) that with new releases Apache Commons projects use org.apache.commons as Maven
artifact groupId. Please consider aligning commons-dbutils Maven artifacts groupId with this
practice. If decided to use org.apache.commons groupId, for the first release with new groupId
also consider publishing relocation pom file too with old groupId (see [this|http://maven.apache.org/guides/mini/guide-relocation.html#Releasing_the_next_version]
for more info).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message