scala-tools breakage

[Paul Phillips]

To the extent that I can figure out what is happening - and I admit I
never know what's going on - my inability to reach scala-tools is
currently leaving me unable to build, even though I am soliciting
nothing from scala-tools. This is with 0.12.0-M2. If this assessment
is within five approximations of true, and actually regardless of its
truth value, can we please purge all possible references to
scala-tools from the codebase as soon as possible. It seems like this
should have been done long ago. Is there something which stands in
the way? I can do the actual clackety-clack if there's nobody else to
do it.


Here is what I am seeing:

// build.sbt
resolvers += "snapshots" at
"https://oss.sonatype.org/content/repositories/snapshots/"

name := "bippy"

organization := "org.improving"

scalaVersion := "2.10.0-SNAPSHOT"


% sbt -sbt-version 0.12.0-M2 -v update
Detected sbt version 0.12.0-M2
Using /Users/paulp/.sbt/0.12.0-M2 as sbt dir, -sbt-dir to override.
# Executing command line:
java
-Xms1536m
-Xmx1536m
-XX:MaxPermSize=384m
-XX:ReservedCodeCacheSize=192m
-Dsbt.global.base=/Users/paulp/.sbt/0.12.0-M2
-jar
/r/sbt-extras/.lib/0.12.0-M2/sbt-launch.jar
update

[info] Set current project to bippy (in build file:/Users/paulp/scratch/Apr25/)
Getting Scala 2.10.0-SNAPSHOT ...

:: problems summary ::
:::: WARNINGS
module not found: org.scala-lang#scala-compiler;2.10.0-SNAPSHOT

==== local: tried

/Users/paulp/.ivy2/local/org.scala-lang/scala-compiler/2.10.0-SNAPSHOT/ivys/ivy.xml

==== typesafe-ivy-releases: tried

http://repo.typesafe.com/typesafe/ivy-releases/org.scala-lang/scala-compiler/2.10.0-SNAPSHOT/ivys/ivy.xml

==== Maven Central: tried

http://repo1.maven.org/maven2/org/scala-lang/scala-compiler/2.10.0-SNAPSHOT/scala-compiler-2.10.0-SNAPSHOT.pom

==== Scala-Tools Maven2 Snapshots Repository: tried

http://scala-tools.org/repo-snapshots/org/scala-lang/scala-compiler/2.10.0-SNAPSHOT/scala-compiler-2.10.0-SNAPSHOT.pom

module not found: org.scala-lang#scala-library;2.10.0-SNAPSHOT

==== local: tried

/Users/paulp/.ivy2/local/org.scala-lang/scala-library/2.10.0-SNAPSHOT/ivys/ivy.xml

==== typesafe-ivy-releases: tried

http://repo.typesafe.com/typesafe/ivy-releases/org.scala-lang/scala-library/2.10.0-SNAPSHOT/ivys/ivy.xml

==== Maven Central: tried

http://repo1.maven.org/maven2/org/scala-lang/scala-library/2.10.0-SNAPSHOT/scala-library-2.10.0-SNAPSHOT.pom

==== Scala-Tools Maven2 Snapshots Repository: tried

http://scala-tools.org/repo-snapshots/org/scala-lang/scala-library/2.10.0-SNAPSHOT/scala-library-2.10.0-SNAPSHOT.pom

::::::::::::::::::::::::::::::::::::::::::::::

:: UNRESOLVED DEPENDENCIES ::

::::::::::::::::::::::::::::::::::::::::::::::

:: org.scala-lang#scala-compiler;2.10.0-SNAPSHOT: not found

:: org.scala-lang#scala-library;2.10.0-SNAPSHOT: not found

::::::::::::::::::::::::::::::::::::::::::::::


:::: ERRORS
SERVER ERROR: Bad Gateway
url=http://scala-tools.org/repo-snapshots/org/scala-lang/scala-compiler/2.10.0-SNAPSHOT/maven-metadata.xml

SERVER ERROR: Bad Gateway
url=http://scala-tools.org/repo-snapshots/org/scala-lang/scala-compiler/2.10.0-SNAPSHOT/scala-compiler-2.10.0-SNAPSHOT.pom

SERVER ERROR: Bad Gateway
url=http://scala-tools.org/repo-snapshots/org/scala-lang/scala-library/2.10.0-SNAPSHOT/maven-metadata.xml

SERVER ERROR: Bad Gateway
url=http://scala-tools.org/repo-snapshots/org/scala-lang/scala-library/2.10.0-SNAPSHOT/scala-library-2.10.0-SNAPSHOT.pom


:: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
unresolved dependency: org.scala-lang#scala-compiler;2.10.0-SNAPSHOT: not found
unresolved dependency: org.scala-lang#scala-library;2.10.0-SNAPSHOT: not found
Error during sbt execution: Error retrieving required libraries
(see /Users/paulp/.sbt/0.12.0-M2/boot/update.log for complete log)
[error] {file:/Users/paulp/scratch/Apr25/}default-54fae3/*:scala-instance:
xsbti.RetrieveException: Could not retrieve Scala 2.10.0-SNAPSHOT
[error] Total time: 87 s, completed Apr 25, 2012 10:34:42 AM

[Jason Zaugg]

On Wednesday, April 25, 2012 7:36:45 PM UTC+2, Paul Phillips wrote:

To the extent that I can figure out what is happening - and I admit I
never know what's going on - my inability to reach scala-tools is
currently leaving me unable to build, even though I am soliciting
nothing from scala-tools.  This is with 0.12.0-M2.  If this assessment
is within five approximations of true, and actually regardless of its
truth value, can we please purge all possible references to
scala-tools from the codebase as soon as possible.  It seems like this
should have been done long ago.  Is there something which stands in
the way? I can do the actual clackety-clack if there's nobody else to
do it.

https://github.com/harrah/xsbt/commit/fa725e

You can explode sbt.boot.properties out of the JAR, edit this, and refer to it by adding @custom.boot.properties to the command line.

It's probably worth back-publishing some old launcher JARs with this change, though.

-jason

 

[Paul Phillips]

On Wed, Apr 25, 2012 at 11:03 AM, Jason Zaugg <jza...@gmail.com> wrote:
> It's probably worth back-publishing some old launcher JARs with this change,
> though.

Not to mention applying that patch to the
not-yet-released-unless-I-missed-it 0.12 branch.

% git branch -r --contains fa725ef9c9d540e759be381b1888da6091e4a5b1
origin/0.13

[Scott Clasen]

This seems to be biting a bunch of people today

Any way we can get an 0.11.3 with all refs to scala tools removed?

[Scott Clasen]

Or convince someone to have the 

http://scala-tools.org/repo-releases/

and

http://scala-tools.org/repo-snapshots/

return an instant 404 rather than a 502 after 30 sec?

[benmccann]

+1  I'm using Play framework and can't get any work done today at all.  I'm still not sure of the root cause, but scala-tools being down is towards the top of my list of suspicions.  I would really love to see 0.11.2 republished with the fix or an 0.11.3 with the fix.  I might be dead in the water until then.

[Paul Phillips]

On Wed, Apr 25, 2012 at 5:36 PM, benmccann <benjamin...@gmail.com> wrote:
> +1  I'm using Play framework and can't get any work done today at all.  I'm
> still not sure of the root cause, but scala-tools being down is towards the
> top of my list of suspicions.  I would really love to see 0.11.2 republished
> with the fix or an 0.11.3 with the fix.  I might be dead in the water until
> then.

I've rebuilt 0.11.2 to use sonatype. Download the launcher here:

https://github.com/downloads/paulp/sbt-extras/sbt-launch-no-scala-tools-0.11.2.jar

[Heiko Seeberger]

On Apr 26, 2012, at 2:36 AM, benmccann wrote:

> +1 I'm using Play framework and can't get any work done today at all. I'm still not sure of the root cause, but scala-tools being down is towards the top of my list of suspicions. I would really love to see 0.11.2 republished with the fix or an 0.11.3 with the fix. I might be dead in the water until then.

A 0.11.3 release would make ALL current plugins (built against 0.11.2) unusable.

Let's better try work around this issue by configuring sbt 0.11.2 to not use Scala-Tools.org. Jason already pointed out how to do that.

Heiko

[Johannes Rudolph]

FYI: We found that even using paulp's launcher for 0.11 there are still references to scala tools left in the `external-resolvers` key. We are now trying this line in both ~/.sbt/user.sbt and ~/.sbt/plugins/plugins.sbt to get rid of those:

externalResolvers ~= (_ filterNot (_.name == "Scala-Tools Maven2 Repository"))

Johannes

[Konrad Malawski]

Hey guys,

We've tried both methods - excluding externalResolvers and also the modified boot.properties sadly sbt still tries to reach out to scala-tools... (for snapshot dependencies). Well I do know that it's not the best idea to have snapshot dependencies at all, but we do have one or two which we can't quickly resolve sadly.

Did anyone figure out a way to solve this problem yet?

We're also trying at the moment - will report back if we find a way.

PS: If I'd start a nexus instance and repackage those problematic dependencies as "not snapshots" that cold possibly resolve this issue, right? We don't yet have a nexus instance but I'd like to have one anyway I guess - esp. in such situations :-)

--

Cheers,

Konrad Malawski

[Johannes Rudolph]

On Thu, Apr 26, 2012 at 12:32 PM, Konrad Malawski <kto...@gmail.com> wrote:
> PS: If I'd start a nexus instance and repackage those problematic
> dependencies as "not snapshots" that cold possibly resolve this issue,
> right? We don't yet have a nexus instance but I'd like to have one anyway I
> guess - esp. in such situations :-)

The question is if you know a place where the snapshots _are_
published since the time that scala-tools.org is down which is now
several months. Many projects have moved to sonatype since. If this is
the case for your dependencies it should suffice to add the OSS
sonatype snapshot repository to your resolvers (which scala-tools.org
redirected to in the last months) instead of the scala-tools snapshots
one.

--
Johannes

-----------------------------------------------
Johannes Rudolph
http://virtual-void.net

[Marius Seritan]

A quick hack

echo "127.0.0.1       scala-tools.org" >> /etc/hosts

Marius

[Brett Cavé]

Or artifactory :)

Sent via my BlackBerry

---

From: Konrad Malawski <kto...@gmail.com>

Sender: simple-b...@googlegroups.com

Date: Thu, 26 Apr 2012 03:32:30 -0700 (PDT)

To: <simple-b...@googlegroups.com>

ReplyTo: simple-b...@googlegroups.com

Subject: Re: [sbt] scala-tools breakage

--
You received this message because you are subscribed to the Google Groups "simple-build-tool" group.
To view this discussion on the web visit https://groups.google.com/d/msg/simple-build-tool/-/RoMSycFqPqYJ.
To post to this group, send email to simple-b...@googlegroups.com.
To unsubscribe from this group, send email to simple-build-t...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/simple-build-tool?hl=en.

[Konrad Malawski]

A follow up to the issue: after applying all the tips found in this thread and waiting a day... It resolved "itself" :-)

So if anyone bumps into these kind of problems, thats the way to go.

Thanks for the tips guys :)

--

Cheers,

Konrad

On Wednesday, April 25, 2012 7:36:45 PM UTC+2, Paul Phillips wrote: