Bart Molenkamp wrote:
The problem is in fop 0.20.5, which has a dependency to avalon-framework
4.0,
...
batik:batik-transcoder:jar:1.6-1:compile (selected for compile)
fop:fop:jar:0.20.5:compile (selected for compile)
xml-apis:xml-apis:jar:1.0.b2:compile (removed - nearer found: 1.3.02)
xerces:xercesImpl:jar:2.2.1:compile (removed - nearer found: 2.8.0)
batik:batik-1.5-fop:jar:0.20-5:compile (selected for compile)
avalon-framework:avalon-framework:jar:4.0:compile (selected for
compile)
...
When including the batik block, you can exclude the dependency like you
said:
<dependency>
<groupId>org.apache.cocoon</groupId>
<artifactId>cocoon-batik-impl</artifactId>
<version>1.0.0-SNAPSHOT</version>
<exclusions>
<exclusion>
<groupId>avalon-framework</groupId>
<artifactId>avalon-framework</artifactId>
</exclusion>
</exclusions>
</dependency>
This works fine, the avalon-framework-4.0.jar is not included with the
webapp or block anymore.
But I'm wondering, isn't there any global setting that will exclude the
jars, no matter from which dependency path they come? Or do I have to
declare this for every dependency that includes
avalon-framework-4.0.jar?
No, unfortunatly not. Maybe Maven 2.1 will provide a solution, at least it was
discussed some time ago.
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
___________________________________________________________
Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
