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

Building locally leads to sbt resolve issues #6782

Closed
ghost opened this issue Dec 6, 2016 · 10 comments
Closed

Building locally leads to sbt resolve issues #6782

ghost opened this issue Dec 6, 2016 · 10 comments

Comments

@ghost
Copy link

ghost commented Dec 6, 2016

Play Version (2.5.x / etc)

2.6.0-SNAPSHOT

API (Scala / Java / Neither / Both)

Neither

Operating System (Ubuntu 15.10 / MacOS 10.10 / Windows 10)

Use uname -a if on Linux.
Linux myAwesomeSystemName 4.8.11-1-ARCH #1 SMP PREEMPT Sun Nov 27 09:26:14 CET 2016 x86_64 GNU/Linux

JDK (Oracle 1.8.0_72, OpenJDK 1.8.x, Azul Zing)

Paste the output from java -version at the command line.

Scala code runner version 2.12.1-20161205-201300-2787b47 -- Copyright 2002-2016, LAMP/EPFL and Lightbend, Inc.

openjdk version "1.8.0_112"
OpenJDK Runtime Environment (build 1.8.0_112-b15)
OpenJDK 64-Bit Server VM (build 25.112-b15, mixed mode)

Building currently leads to:
[info] Resolving org.scala-sbt#sbt-launch;0.13.13 ...
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: UNRESOLVED DEPENDENCIES ::
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: com.typesafe.sbt#sbt-twirl;1.3.0: not found
[warn] :: com.typesafe.sbt#sbt-native-packager;1.1.1: not found
[warn] :: com.typesafe.sbt#sbt-web;1.3.0: not found
[warn] :: com.typesafe.sbt#sbt-js-engine;1.1.3: not found
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn]
[warn] Note: Some unresolved dependencies have extra attributes. Check that these dependencies exist with the requested attributes.
[warn] com.typesafe.sbt:sbt-twirl:1.3.0 (scalaVersion=2.12, sbtVersion=0.13)
[warn] com.typesafe.sbt:sbt-native-packager:1.1.1 (scalaVersion=2.12, sbtVersion=0.13)
[warn] com.typesafe.sbt:sbt-web:1.3.0 (scalaVersion=2.12, sbtVersion=0.13)
[warn] com.typesafe.sbt:sbt-js-engine:1.1.3 (scalaVersion=2.12, sbtVersion=0.13)
[warn]
[warn] Note: Unresolved dependencies path:
[warn] com.typesafe.sbt:sbt-twirl:1.3.0 (scalaVersion=2.12, sbtVersion=0.13) (/home/myAwesomeUsername/playframework/framework/build.sbt#L178)
[warn] +- com.typesafe.play:sbt-plugin:2.6.0-SNAPSHOT (scalaVersion=2.12, sbtVersion=0.13)
[warn] com.typesafe.sbt:sbt-native-packager:1.1.1 (scalaVersion=2.12, sbtVersion=0.13) (/home/myAwesomeUsername/playframework/framework/build.sbt#L178)
[warn] +- com.typesafe.play:sbt-plugin:2.6.0-SNAPSHOT (scalaVersion=2.12, sbtVersion=0.13)
[warn] com.typesafe.sbt:sbt-web:1.3.0 (scalaVersion=2.12, sbtVersion=0.13) (/home/myAwesomeUsername/playframework/framework/build.sbt#L178)
[warn] +- com.typesafe.play:sbt-plugin:2.6.0-SNAPSHOT (scalaVersion=2.12, sbtVersion=0.13)
[warn] com.typesafe.sbt:sbt-js-engine:1.1.3 (scalaVersion=2.12, sbtVersion=0.13) (/home/myAwesomeUsername/playframework/framework/build.sbt#L178)
[warn] +- com.typesafe.play:sbt-plugin:2.6.0-SNAPSHOT (scalaVersion=2.12, sbtVersion=0.13)
[trace] Stack trace suppressed: run last SBT-Plugin/:update for the full output.
[error] (SBT-Plugin/
:update) sbt.ResolveException: unresolved dependency: com.typesafe.sbt#sbt-twirl;1.3.0: not found
[error] unresolved dependency: com.typesafe.sbt#sbt-native-packager;1.1.1: not found
[error] unresolved dependency: com.typesafe.sbt#sbt-web;1.3.0: not found
[error] unresolved dependency: com.typesafe.sbt#sbt-js-engine;1.1.3: not found
[error] Total time: 10 s, completed Dec 6, 2016 9:49:08 PM

I just downloaded a fresh copy of playframework, without any modifications. Also see: http://stackoverflow.com/questions/40990256/cant-download-sbt-plugin-2-5-4-using-activator-on-osx-platform

I can connect to any of those repos, but they are indeed empty or the path is invalid

@ghost ghost changed the title Building locally leads to Building locally leads to sbt resolve issues Dec 6, 2016
@wsargent
Copy link
Member

wsargent commented Dec 6, 2016

Please provide a repeatable test case so we can reproduce it locally.

@ghost
Copy link
Author

ghost commented Dec 6, 2016

repeatable test case for me (tried on my local machine (os as mentioned above) and on windows 7 even via mobile hotspot instead of my wired connection):

  1. git clone git://github.com/playframework/playframework.git
  2. cd playframework/framework
  3. sbt
  4. +publishLocal

or if you want +++2.12.0 publishLocal or +++2.12.1 publishLocal or with +++2.11.8 publishLocal

Always get the same error. (tried to repeat multiple times now, while deleting whole repository and cloning again, also deleted .ivy2 folder and sbt cache and whatnot)

@schmitch
Copy link
Contributor

schmitch commented Dec 6, 2016

@RookieMaus
actually I've just setup a whole new virtual machine centos and didn't had any error.
However on my development mac I had this error at around 21:48 and actually on the new virtual machine it took really really long to download sbt from bintray/akami so I actually copied it, after that it looked like the repositories gone back to normal so I would suggest trying it again.

@ghost
Copy link
Author

ghost commented Dec 7, 2016

@schmitch thanks, but no luck. Doesn't matter what I try. Again I deleted cache and whatnot and first time it looks like it completes successfully, but still sbt cannot be resolved, second time I build I get that unresolved dependency shit.

Well, now that I tried every proposed option I will just wait. Maybe the gods are merciful and I can compile it successfully someday.

(the only thing I wonder about is this: [warn] Credentials file /home/rookiemaus/.bintray/.credentials does not exist

@schmitch
Copy link
Contributor

schmitch commented Dec 7, 2016

Actually this line can be ignored. Also if you use sbt you should have no problem.
I actually encourage you to use the Mailing List, since this is not a bug and we only track issue's here and not help questions, these can be asked freely on the mailing list.

(even travis-ci can actually find all the dependencies https://travis-ci.org/schmitch/playframework/builds/182131146)
And if you just want to test 2.12 you can use a snapshot: https://www.playframework.com/documentation/2.5.x/Repositories#Accessing-snapshots

@schmitch schmitch closed this as completed Dec 7, 2016
@ghost
Copy link
Author

ghost commented Dec 8, 2016

Actually, no, 2.12 support is not the only thing I am after. But thanks anyway.

Apart from that, do I have to manually scan the repository to find out what is the latest snapshot version? Because "com.typesafe.play#sbt-plugin;2.6.0-SNAPSHOT" cannot be resolved there either :(

But alas, on to the mailing list or some chat

@wsargent
Copy link
Member

wsargent commented Dec 9, 2016

If you're having issues downloading sbt-twirl from the remote server e.g. sonatype is hiccuping, you can always build from source:

git clone https://github.com/playframework/twirl.git
cd twirl
git checkout -b 1.3.0 1.3.0
sbt +compile +publishLocal

@wsargent
Copy link
Member

wsargent commented Dec 9, 2016

I think this could be 2.12 related.

[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[warn]  ::          UNRESOLVED DEPENDENCIES         ::
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[warn]  :: com.typesafe.sbt#sbt-twirl;1.3.0: not found
[warn]  :: com.typesafe.sbt#sbt-native-packager;1.1.1: not found
[warn]  :: com.typesafe.sbt#sbt-web;1.3.0: not found
[warn]  :: com.typesafe.sbt#sbt-js-engine;1.1.3: not found
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[warn]
[warn]  Note: Some unresolved dependencies have extra attributes.  Check that these dependencies exist with the requested attributes.
[warn]          com.typesafe.sbt:sbt-twirl:1.3.0 (scalaVersion=2.12, sbtVersion=0.13)
[warn]          com.typesafe.sbt:sbt-native-packager:1.1.1 (scalaVersion=2.12, sbtVersion=0.13)
[warn]          com.typesafe.sbt:sbt-web:1.3.0 (scalaVersion=2.12, sbtVersion=0.13)
[warn]          com.typesafe.sbt:sbt-js-engine:1.1.3 (scalaVersion=2.12, sbtVersion=0.13)
[warn]
[warn]  Note: Unresolved dependencies path:
[warn]          com.typesafe.sbt:sbt-twirl:1.3.0 (scalaVersion=2.12, sbtVersion=0.13) (D:\work\playframework\master\framework\build.sbt#L178)
[warn]            +- com.typesafe.play:sbt-plugin:2.6.0-SNAPSHOT (scalaVersion=2.12, sbtVersion=0.13)
[warn]          com.typesafe.sbt:sbt-native-packager:1.1.1 (scalaVersion=2.12, sbtVersion=0.13) (D:\work\playframework\master\framework\build.sbt#L178)
[warn]            +- com.typesafe.play:sbt-plugin:2.6.0-SNAPSHOT (scalaVersion=2.12, sbtVersion=0.13)
[warn]          com.typesafe.sbt:sbt-web:1.3.0 (scalaVersion=2.12, sbtVersion=0.13) (D:\work\playframework\master\framework\build.sbt#L178)
[warn]            +- com.typesafe.play:sbt-plugin:2.6.0-SNAPSHOT (scalaVersion=2.12, sbtVersion=0.13)
[warn]          com.typesafe.sbt:sbt-js-engine:1.1.3 (scalaVersion=2.12, sbtVersion=0.13) (D:\work\playframework\master\framework\build.sbt#L178)
[warn]            +- com.typesafe.play:sbt-plugin:2.6.0-SNAPSHOT (scalaVersion=2.12, sbtVersion=0.13)

Note that this only happens in the publishLocal stage of the system.

Twirl is still running on Interplay 1.2.0, so I wonder if that could be the problem. Will upgrade to 1.3.0 and Scala 2.12.1

@wsargent wsargent reopened this Dec 9, 2016
@wsargent
Copy link
Member

wsargent commented Dec 9, 2016

See playframework/twirl#126

@ghost
Copy link
Author

ghost commented Dec 16, 2016

And, does it work for you now? Here it worked once (seemingly randomly after I deleted my .m2 folder) and then never again.

I am not even sure what happens. If I delete my .m2 folder before compiling it seems to work, but SBT finishes (with success) and there are still a lot of modules missing. Then rerun +++2.12.1 publishLocal but the sbt-plugin simply can't be compiled... rest seems to be done then.

Workarounds like: http://stackoverflow.com/questions/26205825/why-does-the-build-fail-with-unresolved-dependency-com-typesafe-sbtsbt-native do not work for me :(

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

2 participants