Cross build for 2.9.1-1

[sbt]

Cross build for 2.9.1-1

[jsuereth]

2.9.1 is binary compatible, so you should be able to directly use the
existing artifact. Let me know if you have issues.
On Mar 14, 2012 2:25 PM, "Gregg Carrier" <
[email protected]>
wrote:

Hey Josh -

Any plans to cross-build against 2.9.1-1. We're on that version of Scala
due to some Java interop issues with 2.9.1 I built the Git plugin
internally and we can use that, but I didn't know if it might be useful to
others to have an official binary. Thanks!

---

Reply to this email directly or view it on GitHub:
https://github.com/sbt/sbt-git-plugin/issues/12

[JanxSpirit]

right, but SBT doesn't want to resolve it in 2.9.1-1 based projects. Is there a way to force SBT to use the 2.9.1 version? Thanks.

[jsuereth]

Are you using it as a library or a plugin? If it's a plugin, it can use the SBT version, which is locked down to 2.9.1.

If you're using it a user-level-plugin, you should use ~/.sbt/plugins/plugins.sbt not ~/.sbt/plugins.sbt. Can you show me your build setup and the error message?

[JanxSpirit]

I have the following in ~/.sbt/plugins/plugins.sbt (the docs say use ~/.sbt/plugins.sbt):

resolvers += Resolver.url("scalasbt", new URL("http://scalasbt.artifactoryonline.com/scalasbt/sbt-plugin-releases"))(Resolver.ivyStylePatterns)

resolvers += "jgit-repo" at "http://download.eclipse.org/jgit/maven"

addSbtPlugin("com.jsuereth" % "sbt-git-plugin" % "0.4")

That gives me:

[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: UNRESOLVED DEPENDENCIES ::
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: com.jsuereth#sbt-git-plugin;0.5-SNAPSHOT: not found
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn]
[warn] Note: Some unresolved dependencies have extra attributes. Check that these dependencies exist with the requested attributes.
[warn] com.jsuereth:sbt-git-plugin:0.5-SNAPSHOT (sbtVersion=0.11.2, scalaVersion=2.9.1-1)

[jsuereth]

You have a dependency on the git plugin 0.5-SNAPSHOT hiding somewhere (look
at the error message).

I'll update the docs ASAP! Thanks for the catch. I'm probably causing
this issue with terrible documentation.

[JanxSpirit]

Ah, OK - that's the version I built and deployed locally, so that was in my in-house plugin with that reference. I pulled that out and now the ~/.sbt/plugins/plugins.sbt approach seems to work. So I think in this case, the original original problem was specifying the plugin in ~/.sbt/plugins.sbt.

Thanks for clarifying the behavior difference in those two files.

[jsuereth]

No problem. I myself used to be confused, hence the bad documentation!