On Apr 28, 2014, at 7:24 AM, Josh Suereth <joshua.suer...@gmail.com> wrote:
> > >> You should refer to >> http://www.scala-sbt.org/release/docs/Detailed-Topics/Library-Management.htmlto >> see what you can do to provide this geoapi.version to the resolution >> process. >> >> I do not see anything obvious, maybe create a variable geoapi.version := >> “some.version” in your build.sbt ? >> >> from this web page http://www.geoapi.org/maven.html I infer that 3.0.0 is >> one of the possible values for this version of the org.opengis dependency. >> >> > We expose a `dependencyOverrides` setting that would hit the conflict > resolver, but I think that's too late in the resolution process (I've only > begun digging into the ResovleEngine code and I haven't gotten to > `fetchDependencies` yet). Is there a way to feed these properties into > ivy so they get used? If so, we can provide that API to our users. The class PomReader inside ivy perform property substitutions, but only with key/values defined in the properties section of the POM.xml and with other properties which ivy can infer from the pom itself such as the the groupid, partent artifact id, … One would need to make a code change inside ivy to be able to inject all ivy variables or a subset of the variables in the m2 resolution process. Maarten and Nicolas please correct me if I am wrong. Antoine > > > Thanks! > - Josh
