Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Mon, 9 Jul 2012 11:44:36 +0000 (UTC)
From: "Stevo Slavic (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <66838060.22403.1341834276021.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <705182026.19903.1341747094371.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Updated] (DBUTILS-92) Align maven groupId with rest of the
 apache commons projects
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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