Jorg Heymans napisał(a):
http://jira.codehaus.org/browse/MECLIPSE-262 seems to be somewhat
similar to our problem, I've added our findings there.
Thanks Jorg.
For now i've excluded commons-logging explicitly from commons-jxpath, it
is brought in by several other blocks anyway.
I'm puzzled
Grzegorz Kossakowski wrote:
For now i've excluded commons-logging explicitly from commons-jxpath, it
is brought in by several other blocks anyway.
I'm puzzled now a little. Do we have some exclusion guidelines? Previously, I
thought we had to exclude only
avalon-framework but you excluded
Grzegorz Kossakowski wrote:
I also tried dependency plug-in already and had the same results as you.
It does not mention dependency we are talking about. I have no idea why.
However, I'm almost sure. Try mvn eclipse:eclipse and import project.
You'll see avalon-framework-4.1.3.jar in build
Jorg Heymans wrote:
It seems that the eclipse plugin is using some different (buggy)
dependency resolution mechanism. Don't have time now to investigate
further, will have another look later (perhaps its a confirmed bug in
the plugin?)
http://jira.codehaus.org/browse/MECLIPSE-262 seems to
Hello,
I'm struggling now with transitive dependencies and exclusions in Cocoon.
The problem is that (for example) cocoon-sitemap-impl has dependency on
commons-jxpath which depends on commons-logging. The last one, depends
on avalon-framework:avalon-framework which should be excluded.
In our
Grzegorz Kossakowski wrote:
I'm struggling now with transitive dependencies and exclusions in Cocoon.
The problem is that (for example) cocoon-sitemap-impl has dependency on
commons-jxpath which depends on commons-logging. The last one, depends
on avalon-framework:avalon-framework which should
Jorg Heymans napisał(a):
Neither dependency:resolve nor dependency:analyze list
avalon-framework:avalon-framework as an included dependency (I
executed the plugin from the block directory). Are you sure it comes
from that block ?
I also tried dependency plug-in already and had the same
