cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Grzegorz Kossakowski <g...@tuffmail.com>
Subject Re: [jira] Commented: (COCOON-1975) cocoon-core-M2 could not be runned because of missing dependencies on avalon-framework-api-4.3 and excalibur-instrument-api-2.1
Date Fri, 29 Dec 2006 14:13:42 GMT
Reinhard Poetz napisaƂ(a):
> Reinhard Poetz (JIRA) wrote:
>>     [ 
>> http://issues.apache.org/jira/browse/COCOON-1975?page=comments#action_12461377 
>> ]             Reinhard Poetz commented on COCOON-1975:
>> ----------------------------------------
>>
>> Stupid Maven. It doesn't resolve the transitive dependencies 
>> correctly. We have to release cocoon-core again where we set the 
>> dependencies on avalon-framework-api and excalibur-instrument 
>> explicitly.
>
> I can reproduce this, today. I could swear that it worked when I cut 
> the release two weeks ago also with an empty local repository.
>
> Any idea what's going on here?
It would be great understand what is the reason for this behavior in 
order to avoid such situations in the future. I can invest some time 
(this free time was meant to be spent on writing docs, but now there is 
nothing working to document...) in this issue but I'm not sure what 
should I start from.
Any hints how to debug Maven's dependency resolution? Do you have idea 
why installing trunk version of modules impacts resolving dependencies 
of core-M2?

-- 
Grzegorz Kossakowski

Mime
View raw message