Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

module not found com.artima.supersafe#sbtplugin;1.1.1 with scala 2.12.1 #64

Open
ghost opened this issue Dec 28, 2016 · 12 comments
Open

Comments

@ghost
Copy link

ghost commented Dec 28, 2016

I followed the installation instructions:

$ cat ~/.sbt/0.13/global.sbt 

resolvers += "Artima Maven Repository" at "http://repo.artima.com/releases"
$ cat plugins.sbt 

addSbtPlugin("com.artima.supersafe" % "sbtplugin" % "1.1.1")
$ cat build.sbt 
name := "qb"

version := "1.0"

scalaVersion := "2.12.1"

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

lazy val akkaVersion = "2.4.16"

libraryDependencies ++= Seq(
  "org.eclipse.jgit" % "org.eclipse.jgit" % "4.5.0.201609210915-r",
  "com.typesafe.akka" %% "akka-actor" % akkaVersion,
  "com.typesafe.akka" %% "akka-contrib" % akkaVersion,
  "com.typesafe.akka" %% "akka-testkit" % akkaVersion,
  "org.scalactic" %% "scalactic" % "3.0.1",
  "org.scalatest" %% "scalatest" % "3.0.1" % "test",
  "junit" % "junit" % "4.12" % "test",
  "com.novocode" % "junit-interface" % "0.11" % "test"
)

When I trigger build in sbt, I get this output:

[info] Resolving com.artima.supersafe#sbtplugin;1.1.1 ...
[warn]  module not found: com.artima.supersafe#sbtplugin;1.1.1
[warn] ==== local: tried
[warn]   /home/valir/.ivy2/local/com.artima.supersafe/sbtplugin/scala_2.12/sbt_0.13/1.1.1/ivys/ivy.xml
[warn] ==== public: tried
[warn]   https://repo1.maven.org/maven2/com/artima/supersafe/sbtplugin_2.12_0.13/1.1.1/sbtplugin-1.1.1.pom
[warn] ==== Artima Maven Repository: tried
[warn]   http://repo.artima.com/releases/com/artima/supersafe/sbtplugin_2.12_0.13/1.1.1/sbtplugin-1.1.1.pom
[warn] ==== jgit-repo: tried
[warn]   http://download.eclipse.org/jgit/maven/com/artima/supersafe/sbtplugin_2.12_0.13/1.1.1/sbtplugin-1.1.1.pom
[info] Resolving jline#jline;2.14.1 ...
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[warn]  ::          UNRESOLVED DEPENDENCIES         ::
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[warn]  :: com.artima.supersafe#sbtplugin;1.1.1: not found
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[warn]
[warn]  Note: Some unresolved dependencies have extra attributes.  Check that these dependencies exist with the requested attributes.
[warn]          com.artima.supersafe:sbtplugin:1.1.1 (scalaVersion=2.12, sbtVersion=0.13)
[warn]
[warn]  Note: Unresolved dependencies path:
[warn]          com.artima.supersafe:sbtplugin:1.1.1 (scalaVersion=2.12, sbtVersion=0.13) (/home/valir/soft/src/quickbuild/qb/plugins.sbt#L2-3)
[warn]            +- default:qb_2.12:1.0
[trace] Stack trace suppressed: run last *:update for the full output.
[error] (*:update) sbt.ResolveException: unresolved dependency: com.artima.supersafe#sbtplugin;1.1.1: not found
[error] Total time: 3 s, completed 28.12.2016 22:53:23

If I change the scalaVersion variable to 2.10.2 then SBT will resolve the plugin, but that won't work with Akka. So I really need scala 2.12 here.

@BBK-PiJ-2015-87
Copy link

BBK-PiJ-2015-87 commented Feb 6, 2017

I have the same problem. Any updates on it?
Still can't use supersafe plugin with 2.12.1 scala version.

Intellij log:
[warn] ==== Artima Maven Repository: tried
[warn] http://repo.artima.com/releases/com/artima/supersafe/sbtplugin_2.10_0.13/1.1.1/sbtplugin-1.1.1.pom

@WeiWang88
Copy link

After research, I noticed that:

==== Artima Maven Repository: tried
[warn] http://repo.artima.com/releases/com/artima/supersafe/sbtplugin_2.12_0.13/1.1.2/sbtplugin-1.1.2.pom

The plug in was stored at:
http://repo.artima.com/releases/com/artima/supersafe/sbtplugin_2.12/1.1.2/sbtplugin-1.1.2.pom

Can scalatest solve this issue?

@vreuter
Copy link

vreuter commented Feb 15, 2018

You could try with a newer sbt and adding the resolver to the corresponding newer .sbt folder. I was having a similar issue, using sbt 1.1.1. When I modified added global.sbt to ~/.sbt/1.0 with the resolver originally mentioned, it worked.

@ChaosWars
Copy link

IT only works if you add the resolver to a global SBT config file. Apparently there is a difference in how plugins are resolved, depending on where the resolvers are added. Which is insane.

@andreabisello
Copy link

same problem , 2 years after.

@cheeseng
Copy link
Contributor

Sorry not sure why I didn't receive notification of this thread until now, can you try with the latest version which is 1.1.7 following the guide here?

https://www.artima.com/supersafe_user_guide.html

@mskonovalov
Copy link

So it works if you add resolvers to both plugins.sbt and build.sbt

@AndreasPresthammer
Copy link

The only version of com.artima.supersafe:sbtplugin which is hosted is the 1.1.10 version. No idea why they don't host the other versions in their private repo.

The current scalatest installation instruction for supersafe is thus currently broken.

@gkirill
Copy link

gkirill commented May 9, 2020

I was able to get it running by doing the following

Add the following line to project/plugins.sbt

addSbtPlugin("com.artima.supersafe" % "sbtplugin" % "1.1.10")

Add the following line to build.sbt

resolvers += "Artima Maven Repository" at "https://repo.artima.com/releases"

And I did not have to install anything globally.

@thekemlin
Copy link

So it works if you add resolvers to both plugins.sbt and build.sbt

It work!

@solarmosaic-kflorence
Copy link

This isn't resolving in our Artifactory repository:

Failed to transform pom file: The target deployment path 'com/artima/supersafe/sbtplugin_2.12_1.0/1.1.10/sbtplugin-1.1.10.pom' does not match the POM's expected path prefix 'com/artima/supersafe/sbtplugin/1.1.10'. Please verify your POM content for correctness and make sure the source path is a valid Maven repository root path.

@solarmosaic-kflorence
Copy link

solarmosaic-kflorence commented Oct 9, 2020

Related to scalatra/sbt-scalatra#54

It seems like the best way to solve this is to publish the SBT plugin ivy style instead of maven style. For now, I can check "Suppress POM Consistency Checks" for this repository in Artifactory as a workaround, although this is not ideal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests