Carsten Ziegeler wrote:
> 1) Avalon framework. Up to version 4.1.0 (or something) Avalon had one
> big jar: the avalon framework. Then starting with 4.1.1 they splitt this
> into two jar files: api and impl. But for convenience they provide both
> versions, so for example, you have
> avalon-framework-4.2.0.jar
> avalon-framework-api-4.2.0.jar
> avalon-framework-impl-4.2.0.jar
> 
> Now Cocoon depends on 4.2.0 api and impl which of course works fine. We
> use several other projects, that depend on avalon-framework-4.1.5. As
> this is a different identifier for the jar we end up with
> avalon-framework-4.1.5 and api/impl from 4.2.0 resulting in errors as
> 4.1.5 is loaded before the other two jars! (Compilation works fine of
> course).
> All poms are imho correct. And there are several projects having these
> different dependencies. So everywhere specifying exclude statements
> can't be the solution.
> 
Just in addition, a similar problem exists with Ant. Up to 1.5.x Ant
provided two jars, ant and ant-optional. From 1.6 Ant splitted up the
optinal jar into several ones. Now if your project depends on ant 1.6.5
and let's say ant-optional-trax-1.6.5 while a project you depend on,
depends on ant-optional.1.5.3 again you have all three jars resulting in
errors at runtime.

Carsten
-- 
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to