Re: Specifying version range for dependency causes resolver error; maven-metadata.xml on central looks wrong - how do I make ranges work?

Hi Christian, Le jeudi 28 septembre 2017, 11:05:10 CEST Christian Balzer a écrit : > Hi Hervé, > > Thanks for your help. I'm not sure I like the answer, to be honest, looks you clearly understood the answer :) > although I perfectly understand the reasoning. I think that we need to better

Re: Specifying version range for dependency causes resolver error; maven-metadata.xml on central looks wrong - how do I make ranges work?

Hi Hervé, Thanks for your help. I'm not sure I like the answer, to be honest, although I perfectly understand the reasoning. I'll get in touch with the library maintainers of those libraries my project uses (hoping they all still have maintainers). The list of inconsistencies looks rather

Re: Specifying version range for dependency causes resolver error; maven-metadata.xml on central looks wrong - how do I make ranges work?

Hi, Here is a list of inconsistencies (expected to be extensive) in central between maven-metadata.xml and what is in the repo [1] (updated daily): in this file, each "+" is about a version that is available in the repo but not referenced in maven-metadata.xml, and each "-" is about a version

Re: Specifying version range for dependency causes resolver error; maven-metadata.xml on central looks wrong - how do I make ranges work?

Good morning all, Here are the versions I found yesterday that are not listed in their respective maven-metadata.xml files: 1.9.13: http://central.maven.org/maven2/org/codehaus/jackson/jackson-core-asl/maven-metadata.xml 1.9.13:

Re: Specifying version range for dependency causes resolver error; maven-metadata.xml on central looks wrong - how do I make ranges work?

Hi Karl Heinz, Thanks for your help. On Tue, Sep 26, 2017 at 4:23 PM, Karl Heinz Marbaise wrote: > Hi, > > based on the feedback I got here: > https://issues.sonatype.org/browse/MVNCENTRAL-2721 When I try to open that ticket (even when being logged in on Sonatype's Jira) I

Re: Specifying version range for dependency causes resolver error; maven-metadata.xml on central looks wrong - how do I make ranges work?

Hi, based on the feedback I got here: https://issues.sonatype.org/browse/MVNCENTRAL-2721 It could be only a little time to be fixed in Maven Central.. Kind regards Karl Heinz Marbaise On 26/09/17 13:12, Karl Heinz Marbaise wrote: Hi, On 26/09/17 13:02, Christian Balzer wrote: Hi all, I

Re: Specifying version range for dependency causes resolver error; maven-metadata.xml on central looks wrong - how do I make ranges work?

Hi, On 26/09/17 13:02, Christian Balzer wrote: Hi all, I have a pom.xml file of a legacy program that declares a dependency on an Apache Commons' xml-resolver:xml-resolver via dependency management and a property. The pom file looks essentially like this: 1.2

Specifying version range for dependency causes resolver error; maven-metadata.xml on central looks wrong - how do I make ranges work?

Hi all, I have a pom.xml file of a legacy program that declares a dependency on an Apache Commons' xml-resolver:xml-resolver via dependency management and a property. The pom file looks essentially like this: 1.2 xml-resolver xml-resolver