scalaVersion not taken into account
Open
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 712
- Forks
- 163
- PR merge metrics
- No merged PRs in 30d
Description
I created two projects, each with a different scalaVersion.
In eclipse, both are seen as 2.10.6,
which gives problems when adding dependencies.
build.sbt
lazy val xproject = project.
settings(
scalaVersion := "2.10.6"
)
lazy val yproject = project.
settings(
scalaVersion := "2.11.8"
)
Test with
- Scala-IDE 4.6.0-vfinal-2017-05-16T08:49:17Z-Typesafe
- Scala-IDE 4.5.0-vfinal-2016-12-13T10:59:29Z-Typesafe
on OS X 10.11.6
sbt 0.13.15
sbteclipse 5.1.0
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the sbteclipse handling of scalaVersion and reproduce the issue using the two projects in the build.sbt example, with Scala 2.10.6 and 2.11.8. Inspect the generated Eclipse project definitions and dependency metadata; done means each project reflects its configured Scala version instead of both using 2.10.6.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100