inconsistent update strategies

[harrah]

I recently received a bug report 1 in my plugin about a library dependency not being resolved. I am able to resolve this dependency fine "from" a url 2 when I build my plugin locally. I removed the dependency from my ivy cache and tried to depend on my plugin from a scratch project

set resolvers += "less is" at "http://repo.lessis.me"
set libraryDependencies <+= sbtVersion(v => "me.lessis" %% "coffeescripted-sbt" % "0.1.2-%s".format(v))
update

I get the same dependency resolution error mentioned by this user. I did a little more detective work and found that sbt was doing different things based on whether I was building my plugin and updating or depending on my plugin and updating. I captured the relavant ivy logging in a gist 3 to show you want I mean. It looks like when I build my plugin locally, sbt is aware that my dependency is declared as an artifact with a url and falls back on that

[debug]   using url for org.jcoffeescript#jcoffeescript;1.1!jcoffeescript.jar: http://cloud.github.com/downloads/yeungda/jcoffeescript/jcoffeescript-1.1.jar

This is not the case when adding my plugin as a dep to a project and updating.

I'll try tracking down a more of what happens in the relavent IvyAction code 4 so to try to find discrepancies.

Let me know if anything I'm doing pops out at you.

[harrah]

IMPORTANT This project has moved to https://github.com/sbt/sbt. This issue still exists to avoid dead links, but GitHub limitations prevent the original issue from being correctly preserved here. Please see sbt/sbt#137 for the full issue and to comment.