Bart Molenkamp wrote:
It seems to work. Thanks for that.
However, I think I found another problem related to Eclipse. Batik has a
dependency to rhino:js:1.5R4.1, but cocoon-core has a dependency to
rhino:js:1.6R5. When I build my block, or when I build from the root
pom, Maven builds against 1.6R5 (it removes 1.5R4.1 from the classpath).
This is correct.
But when I build the Eclipse descriptors, it adds rhino:js:1.5R4.1 to
the classpath. That is wrong, IMO. It should add the dependency to
rhino:js:1.6R5 (transitively trough cocoon-core's dependencies).
You can see it for yourself by creating all the eclipse descriptors for
trunk, and then opening the block cocoon-batik-impl (you'll see the
wrong version of rhino:js on the classpath). Is this a known problem, or
better, does anybody know how to solve this?
Try to exclude the dependeny on rhino:js:1.5R4.1 from the batik library and add
explicitly add the dependency on rhino:js:1.6R5. I haven't tried it myself but I
guess it could work.
--
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
