[
https://issues.apache.org/jira/browse/DBUTILS-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13409385#comment-13409385
]
Joerg Schaible commented on DBUTILS-92:
---------------------------------------
A relocation POM is wrong in any case. If DBUTILS 2.0 will be binary
compatible, groupId and artifactId will not change. If it is incompatible, it
will also change the package name and both artifacts are meant to be used at
the same time.
> 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, DBUTILS-92.patch, DBUTILS-92.patch,
> pom.xml, 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
