David,
Sorry if it's not clear.
Artifact commons-dbcp-all is defined as :
<parent>
<groupId>org.apache</groupId>
<artifactId>apache</artifactId>
<version>3</version>
</parent>
<modelVersion>4.0.0</modelVersion>
<artifactId>commons-dbcp-all</artifactId>
<packaging>jar</packaging>
<name>OpenEJB :: Dependencies :: Commons DBCP and Pool</name>
<version>1.3-r699049-SNAPSHOT</version>
[...]
May be I'm wrong but as this artifact does not specify groupId, it will be
the same as the parent. So the result will be
org.apache:commons-dbcp-all:<version>.
But when looking for it's dependency in openejb module, you are looking for
a dependency: org.apache.openejb:commons-dbcp-all:<version>
So from my point of view, you should either:
- add a <groupId>org.apache.openejb</groupId> in commons-dbcp-all
- change openejb dependency to point to <groupId>org.apache</groupId>
In fact, I think the problem comes from the new deps module:
commons-dbcp-all
Jean-Louis
David Blevins wrote:
>
> Hi Jean-Louis,
>
> On Sep 26, 2008, at 10:08 AM, Jean-Louis MONTEIRO wrote:
>
>>
>> Hi,
>>
>> After a recent checkout (this afternoon), I noticed commons-dbcp-all
>> dependency (from the openejb parent module) changed from
>> <dependency>
>> <groupId>org.apache.openejb</groupId>
>> <artifactId>commons-dbcp-all</artifactId>
>> <version>1.3</version>
>> </dependency>
>> to
>> <dependency>
>> <groupId>org.apache.openejb</groupId>
>> <artifactId>commons-dbcp-all</artifactId>
>> <version>1.3-r699049-SNAPSHOT</version>
>> </dependency>
>>
>> But, the openejb/deps/commons-dbcp-all module as the "org.apache"
>> group id.
>> It breaks dependencies management.
>>
>> Can you put it more consistent ?
>
> Not sure I understand. The groupId and artifactId are the same in
> both versions. Do you mean the parent groupId?
>
> -David
>
>
>
--
View this message in context:
http://www.nabble.com/commons-dbcp-all-consistency-problem-tp19690302p19691135.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.
