sbt / sbt/sbt-eclipse

Unable to use version 2.3.0

Open
#171 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Scala
Stars
712
Forks
163
PR merge metrics
No merged PRs in 30d

Description

As of this writing, I'm having issues using version 2.3.0 as instructed in the home/For the impatient section. The error is pasted below - Connection reset. Changing to version 2.2.0 works for me. Note that I had problem installing scala ide for eclipse, similar Connection reset issue. I had to use wget to clone part of the scala ide site to install eclipse plugin. So issue might be my network, but hopefully someone might kind enough to make downloading as robust as wget (auto retries).

eclilpse kepler, scala 2.10.0, sbt 0.13

[info] downloading http://repo1.maven.org/maven2/org/scalaz/scalaz-core_2.10/7.0.2/scalaz-core_2.10-7.0.2.jar ...
[warn] [FAILED ] org.scalaz#scalaz-core_2.10;7.0.2!scalaz-core_2.10.jar(bundle): Connection reset (63697ms)
[warn] [FAILED ] org.scalaz#scalaz-core_2.10;7.0.2!scalaz-core_2.10.jar(bundle): (0ms)
[warn] ==== typesafe-ivy-releases: tried
[warn] http://repo.typesafe.com/typesafe/ivy-releases/org.scalaz/scalaz-core_2.10/7.0.2/bundles/scalaz-core_2.10.jar
[warn] ==== sbt-plugin-releases: tried
[warn] http://repo.scala-sbt.org/scalasbt/sbt-plugin-releases/org.scalaz/scalaz-core_2.10/7.0.2/bundles/scalaz-core_2.10.jar
[warn] ==== local: tried
[warn] /home/barnut/.ivy2/local/org.scalaz/scalaz-core_2.10/7.0.2/bundles/scalaz-core_2.10.jar
[warn] ==== public: tried
[warn] http://repo1.maven.org/maven2/org/scalaz/scalaz-core_2.10/7.0.2/scalaz-core_2.10-7.0.2.jar
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: FAILED DOWNLOADS ::
[warn] :: ^ see resolution messages for details ^ ::
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: org.scalaz#scalaz-core_2.10;7.0.2!scalaz-core_2.10.jar(bundle)
[warn] ::::::::::::::::::::::::::::::::::::::::::::::

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the home/For the impatient instructions and the sbt 0.13 dependency-resolution path, then reproduce the failed scalaz-core_2.10 7.0.2 download using the repositories listed in the report. Done means establishing whether transient connection resets can be handled more robustly, with the version 2.3.0 setup completing successfully or the limitation clearly identified.

Written by the indexing model from the issue text.

Assessment

Tech stack
scala
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.