Hi Khristian, Our Maven / pom support does not cover these symbolic release names yet. At this point, you'd have to resolve this dependency manually or create an alias, e.g.,
STAX_EX = "org.jvnet.staxex:stax-ex:jar:1.6" STAX_EX_RELEASE = "org.jvnet.staxex:stax-ex:jar:RELEASE" # add dependency (for download purposes) artifact(STAX_EX_RELEASE).enhance([artifact(STAX_EX)]) # create alias artifact(STAX_EX_RELEASE).from(repositories.locate(STAX_EX)) The on-going integration with Aether should get us better Maven/pom support... if this is a blocker for you, it could also be implemented in buildr with our custom pom support. Either way, feel free to file an enhancement request or hack something together and submit a patch. alex On Wed, Jan 11, 2012 at 2:37 PM, Khristian <[email protected]> wrote: > I'm building a project with buildr that depends indirectly on the > stax-ex library. The problem is, some dependency seems to be looking > for the RELEASE version of this library. > > It fails with: > > (...) > Downloading org.jvnet.staxex:stax-ex:pom:RELEASE > Buildr aborted! > RuntimeError : Failed to download > org.jvnet.staxex:stax-ex:pom:RELEASE,(...) > > I've noticed that the metadata file for stax-ex has an entry for the > RELEASE version: > (...) > <versioning> > <latest>1.6</latest> > <release>1.6</release> > (...) > > This seems to be related to a recent e-mail sent to the list (though > it only mentions the maven keyword LATEST). > > Any ideas? > Thanks, > > -- > Khristian Alexander Schönrock >
