Re: [sbt] SBT trying to resolve wrong version number for an artifact

[Paul Phillips]

On Tue, Mar 5, 2013 at 2:23 PM, Dian Fay <dian....@gmail.com> wrote:

And here's what SBT is trying to do:

[info] Resolving de.neuland#jade4j;0.3.8 ...

[warn] module not found: de.neuland#jade4j;0.3.8

before it finally spits out the ResolveException since that version doesn't exist. If I plug in a made-up version number for the artifact, it tries to resolve that number -- as far as I've seen, it's only 0.3.2 it turns into something else. Is anyone else able to reproduce this, or am I just going crazy here?

It's a transitive dependency. Notice it's called "jade4j", not "spring-jade4j".

[Dian Fay]

augh, I should have noticed that... adding the Jade4J releases repository fixed it. It's strange though, in my Maven POM I only had the Spring-Jade4J releases repo included. It looks like the resolution mechanism is slightly different?

Thanks!