Hi Folks,
If you change groupId could you please provide a relocation pom in the
old groupId
commons-dbcp:commons-dbcp:1.3 -> org.apache.commons:commons-dbcp-jdbc3:1.3

--
Olivier

2009/11/26 Phil Steitz <phil.ste...@gmail.com>:
> Paul Benedict wrote:
>> Phil,
>>
>> I don't think you should be modifying the version (and groups, really)
>> here. All the artifacts belong to version 1.3.
>>
>> Maven does have a concept of a qualifier, but according to Sonatype,
>> it's only to capture milestone builds:
>> http://www.sonatype.com/books/maven-book/reference/pom-relationships-sect-pom-syntax.html
>>
>> What you have, simply, is, different artifacts.
>
> Makes sense.  Thanks.
>
>  Keep the same groupId
>> and version, just alter the artifact names.
>
> What I was trying to avoid by moving the groupId to
> org.apache.commons for the JDBC 4 artifact was 1.4-1.5 users
> unwittingly upgrading to 1.3 and blowing up.  This is also a change
> we need to make at some point.
>
> Phil
>>
>> JDBC 4 version (JDK 1.6)
>> groupId = org.apache.commons
>> artifactId = commons-dbcp
>> version = 1.3
>>
>> JDBC 3 version (JDK 1.4-1.5)
>> groupId = org.apache.commons
>> artifactId = commons-dbcp-jdbc3
>> version = 1.3
>>
>> Paul
>>
>> On Wed, Nov 25, 2009 at 4:14 PM, Phil Steitz <phil.ste...@gmail.com> wrote:
>>> Phil Steitz wrote:
>>>> I am about to roll an RC and I need to make sure all are OK with the
>>>>  artifact names and repo placement
>>>>
>>>> JDBC 4 version (JDK 1.6)
>>>> groupId org.apache.maven
>>> Oops! I obviously mean commons above :)
>>>> artifactID commons-dbcp
>>>> version 1.3
>>>>
>>>> JDBC 3 version (JDK 1.4-1.5)
>>>> groupId commons-dbcp
>>>> artifactId commons-dbcp
>>>> version 1.3-jdbc3
>>>>
>>>> Giving the 1.3 name to the 1.6 version makes sense as this is the
>>>> main development version.  Moving it gets it into compliance with
>>>> the maven standard and avoids unintended consequences of upgrading
>>>> for 1.4-1.5 users by requiring a bigger change.
>>>>
>>>> Alternatively, we could put descriptors on both and leave placement
>>>> as is. Opinions please.
>>>>
>>>> Phil
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>



-- 
Olivier

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to