6 Commits

Author	SHA1	Message	Date
Mark Harrah	c0b1bb51e6	-Xlint	2013-02-04 17:30:31 -05:00
Mark Harrah	8d11d1087a	Mark the tests failed exception as having already provided feedback	2013-01-28 17:14:53 -05:00
Paolo G. Giarrusso	19aaaea923	Fix compile error in Eclipse ... 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.	2013-01-22 09:05:15 -05:00
Mark Harrah	329b42453b	move Eval test to correct location	2012-12-19 10:17:56 -05:00
Mark Harrah	71f12fbcdb	2.9 compatibility for incremental compilation modules	2012-12-11 14:41:22 -05:00
Grzegorz Kossakowski	ef39aeb9c1	Follow source layout convention supported by Eclipse. ... Moved source files so directory structure follow package structure. That makes it possible to use Scala Eclipse plugin with sbt's source code.	2012-12-07 10:27:08 -08:00