-
Notifications
You must be signed in to change notification settings - Fork 445
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
unresolved dependency: com.typesafe.sbt#sbt-native-packager;1.1.4: not found #1100
Comments
You need to put the
into I recommend the sbt plugins documenation as a good read :) |
@muuki88 @shshankar1 |
I have the same problem after adding plugins in project/plugins.sbt. |
Have you tried the latest version |
https://dl.bintray.com/typesafe/ivy-releases/com.typesafe.sbt/sbt-native-packager/scala_2.12/sbt_1.0/1.3.25/ivys/ivy.xml is an invalid url. Is this related to typesafe moving to lightbend? Going to https://repo.typesafe.com/ tells me that the files are being re-directed. They suggest you include: Resolver.typesafeIvyRepo("releases") https://repo.typesafe.com/typesafe/ivy-releases/ for your plugins. |
did the plugin get moved from "com.typesafe.sbt" to "com.github.sbt"? addSbtPlugin("com.github.sbt" %% "sbt-native-packager" % "1.9.4") |
This issue still seems relevant to the current documentation which points users to download from "com.typesafe". Was only able to figure out the install by finding this thread. |
Expected behaviour
sbt compile should be successful.
Actual behaviour
Required version is not available in artifactory and giving below error:
[warn] ==== Typesafe repository: tried
[warn] http://repo.typesafe.com/typesafe/releases/com/typesafe/sbt/sbt-native-packager_2.11_0.13/1.1.4/sbt-native-packager-1.1.4.pom
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: UNRESOLVED DEPENDENCIES ::
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: com.typesafe.sbt#sbt-native-packager;1.1.4: not found
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
Information
build.sbt:
The text was updated successfully, but these errors were encountered: