Ok. I managed to check. So no, there is no range like in your example from what I see. The dependency tree tells me that com.sun.xml.ws:jaxws-rt:jar:2.1.7 is referencing version 1.2 and that's it.
I just realized that the problem occurs when I'm using the -U option. The help is telling that it "Forces a check for updated releases and snapshots on remote". It's a bit weird that rekeases are checked but why not. BUT why is staxex maven-metadata.xml file the only one the keeps being downloaded? (with groovy-eclipse-batch that also is)??? Some timestamp issue? On 29 May 2013 15:40, Stephen Connolly <stephen.alan.conno...@gmail.com>wrote: > it would look something like <version>[1.7.3,)</version> but most likely it > will be a transitive dependency that some dependency of yours is pulling > in. > > have a look at the output of dependency:tree > > > On 29 May 2013 14:35, Henri Tremblay <henri.tremb...@gmail.com> wrote: > > > A version range? > > > > How can I have a version range in a dependency tree? Aren't dependencies > > always fixed values? > > > > How can I check that? > > > > > > On 29 May 2013 14:34, Stephen Connolly <stephen.alan.conno...@gmail.com > > >wrote: > > > > > I would guess you might have a version range in your dependency tree > > > > > > > > > On 29 May 2013 13:30, Henri Tremblay <henri.tremb...@gmail.com> wrote: > > > > > > > Hi, > > > > > > > > Some of metadata.xml files are downloaded for every build done from > > > > Jenkins. > > > > > > > > I don't know why. One example is org.jvnet.staxex:stax-ex:1.7.1 > > > > > > > > -X doesn't tell me anything > > > > > > > > How can I find out? (including where to put a breakpoint in the maven > > > > source code) > > > > > > > > Thanks > > > > Henri > > > > > > > > > >
