Skip to Content.
Sympa Menu

xom-interest - Re: [XOM-interest] Xom and Jaxen dependency

xom-interest AT lists.ibiblio.org

Subject: XOM API for Processing XML with Java

List archive

Chronological Thread  
  • From: "Steve Loughran" <steve.loughran AT gmail.com>
  • To: xom-interest <xom-interest AT lists.ibiblio.org>
  • Subject: Re: [XOM-interest] Xom and Jaxen dependency
  • Date: Wed, 15 Nov 2006 20:49:34 +0000

On 15/11/06, Adam Constabaris <adamc AT unc.edu> wrote:
.

If you explicitly declare a later version of a dependency in the POM
you're using for a local build, then that will be what's pulled in.

maven2 pulls in the closest version doing a breadth first search.
Different versions at the same distance from root==error. Some
projects (e.g. cocoon) have apparently resorted to declaring extra
dependencies to force updates in.

1. Ivy supports pluggable conflict managers
http://jayasoft.org/ivy/doc/configuration/conflict-managers

2. Ivy lets you declare dependencies on latest version,
"latest.integration", "latest.stable" and "latest.milestone" being
examples. This only makes sense when the artifacts are being generated
locally and you really do want the latest version. When the file is
resolved the real revision is inserted into the final ivy.xml or pom.

-steve




Archive powered by MHonArc 2.6.24.

Top of Page