>
> Finally, some goodies from the Maven dependency handling:
>
> 1.) Let's say you want to use dom4j. You want to use the xpath functionality
> of dom4j. Dom4j needs Jaxen for supporting this. As not everybody uses the
> xpath functionality, Jaxen is an optional dependency of dom4j.
>
> See:
>
http://repo1.maven.org/maven2/dom4j/dom4j/1.6.1/dom4j-1.6.1.pom>
> What do you have to do in the pom.xml to get it into your classpath?
> <dependency>
> <artifactId>dom4j</artifactId>
> ...
> </dependency>
> <dependency>
> <groupId>jaxen</groupId>
> <artifactId>jaxen</artifactId>
> <version>1.1-beta-6</version>
> <optional>true</optional>
> </dependency>
>
>
> You have to declare Jaxen as a first level dependency and the build
> expresses no longer, that Jaxen is used in this project only as a dependency
> of dom4j. Yak!!!! Welcome back in the jar hell!
This is exactly why ivy rocks :-) It solves it nicely by allowing you
to decalre configurations of your package and users of your can
depened on one of the configurations you
defined.
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
