Jason van Zyl wrote:
>>Path to dependency:
>> 1) apache-cocoon:cocoon-core:jar:2.2-SNAPSHOT
>> 2) excalibur-store:excalibur-store:jar:2.1
>> 3) excalibur-fortress:excalibur-fortress-container-api:jar:1.2
>> 4) d-haven-managed-pool:d-haven-managed-pool:jar:1.0
>>
<snip/>
>
> 1) Examine the repo and make sure you're using correct groupIds and
> artifactIds
>
In this case, who is right : the pom declaring
<dependency>
<groupId>d-haven-managed-pool</groupId>
<artifactId>d-haven-managed-pool</artifactId>
<version>1.0</version>
</dependency>
or the maven repository having groupId and artifactId d-haven-mpool ?
As I didn't feel to change the poms, i adjusted my local repository to
match the pom declarations - but this quickly became a pain as I find
more and more dependencies are mismatched :(
> 2) Contact the project in question and see if someone is maintain the
> metadata and if not
could do, but if I have to start sending out emails to get other
projects to fix their poms ... that could quickly become a lengthy
process for a project like Cocoon :-)
Regards
Jorg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
