[jira] [Updated] (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:all-tabpanel ] Stevo Slavic updated DBUTILS-92: Attachment: DBUTILS-92.patch Here's another patch ( [^DBUTILS-92.patch] ) with packages renamed, intended for 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, 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] [Updated] (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:all-tabpanel ] Stevo Slavic updated DBUTILS-92: Attachment: pom.xml DBUTILS-92.patch In this [^DBUTILS-92.patch] artifactId is changed to commons-dbutils2 as well, following same pattern from commons-lang project. Attached is also new relocation [^pom.xml] reflecting changed artifactId. 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] [Updated] (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:all-tabpanel ] Simone Tripodi updated DBUTILS-92: -- Affects Version/s: (was: 1.4) 2.0 Fix Version/s: 2.0 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: 2.0 Reporter: Stevo Slavic Fix For: 2.0 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] [Updated] (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:all-tabpanel ] Stevo Slavic updated DBUTILS-92: Attachment: pom.xml DBUTILS-92.patch Here's [^DBUTILS-92.patch] with changed groupId (and myself listed as contributor), and minimal relocation [^pom.xml]. 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
