mirror of https://github.com/sbt/sbt.git
19aaaea923
Let's consider compile/inc/src/main/scala/sbt/CompileSetup.scala. There are multiple Output types, and according to Eclipse importing xsbti.compile.Output within the package sbt does not work because the import is shadowed by sbt.Output. However, compilation proceeds just fine within SBT. Reproducing the example however gives the same warning, if the files are in the same project. The problem here is probably that the shadowing Output is declared in the same package but in another project, and that seems to give different results in Eclipse and SBT, but relying on that looks fragile. Reading the spec is inconclusive since it doesn't match with Scalac's behavior — see https://groups.google.com/d/topic/scala-internals/-Rquc2HBYLk/discussion . ForkTests has the same behavior as CompileSetup. |
||
|---|---|---|
| .. | ||
| api | ||
| inc | ||
| integration/src/main/scala/sbt/compiler | ||
| interface | ||
| ivy/src/main/scala/sbt/compiler | ||
| persist | ||
| src/main/scala/sbt | ||
| NOTICE | ||