-
Notifications
You must be signed in to change notification settings - Fork 65
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
Installer doesn't fetch sbt launcher #16
Comments
Oh, crap. This is probably related to conscript app depending on the launcher in the normal way instead of being "provided". Without that, the installer does not have it on its classpath and throws an exception. So we need to figure out a different way to configure that, or separate the installer from the launcher-based app. |
The 0.10.0 seems to be here (http://repo.typesafe.com/typesafe/ivy-releases/org.scala-tools.sbt/launcher-interface/0.10.0/) if that's relevant. |
Yeah, the thing is the app doesn't actually need it because the launcher provides the interface. I don't think the typesafe repo is on the standard resolution path, just certain ones. |
I was wondering if adding
in launchconfig makes it recognize. |
Good idea! That works, if you specify the resolution pattern. I've pushed an updated conscript template. mart, could you try running the installer again, then running cs? |
Works for me, thanks. Closing. |
I had a similar issue 'could not find commons-logging'. A retry after clearing the commons-logging directory from my maven repo, and deleting the ~/.ivy2 directory, just worked. Still don't get what went wrong. |
Your local ivy cache can be polluted with bad data, probably from an upstream repository but it's hard to tell because you usually don't become aware of it until later. The only fix is to remove the bad data. We'll try to add some helpful error messages at some point, but this is a really tricky (and fairly rare) problem for conscript and sbt in general. |
The installer runs without error, but when I subsequently try to run 'cs' it fails to resolve the sbt 0.10 launcher.
The text was updated successfully, but these errors were encountered: