[jira] [Commented] (DBUTILS-92) Align maven groupId with rest of the apache commons projects
[ https://issues.apache.org/jira/browse/DBUTILS-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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
[jira] [Commented] (DBUTILS-92) Align maven groupId with rest of the apache commons projects
[ https://issues.apache.org/jira/browse/DBUTILS-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13409451#comment-13409451 ] Stevo Slavic commented on DBUTILS-92: - Agreed, skip publishing relocation pom then. 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
[jira] [Commented] (DBUTILS-92) Align maven groupId with rest of the apache commons projects
[ https://issues.apache.org/jira/browse/DBUTILS-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13408913#comment-13408913 ] Sebb commented on DBUTILS-92: - Unfortunately relocation poms don't work properly (they are not guaranteed to be used), so changing the Maven coords may result in jar hell unless we also change the package name. 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
[jira] [Commented] (DBUTILS-92) Align maven groupId with rest of the apache commons projects
[ https://issues.apache.org/jira/browse/DBUTILS-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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
