dotty - Research platform for new language concepts and compiler technologies for Scala.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Add `Properties` object for dotty testing props and env	Felix Mulder	2017-04-12	1	-8/+16
\|
*	Make inter JVM communication be string based	Felix Mulder	2017-04-12	1	-0/+13
\|
*	Do not hardcode jars path in the tests, instead get them from sbt	Guillaume Martres	2017-01-27	1	-11/+9
\| \| \| \| \|	This is necessary to run the tests with the bootstrapped projects and is just much better than hardcoding them anyway.
*	Bump version from 0.1-SNAPSHOT to 0.1.1-SNAPSHOT	Guillaume Martres	2017-01-08	1	-3/+3
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	This is useful for two reasons: - All published Scala versions are of the form a.b.c and some tooling expect that, like sbt CrossVersion API. - Using 0.1.1 instead of 0.1.0 means that we match the version number of dotty-sbt-bridge, this is simpler and means that in the future sbt could automatically choose the correct version of dotty-sbt-bridge so that the user does not need to specify scalaCompilerBridgeSource in his build.sbt Note: it's awful that we have hardcoded paths to jars and that I had to change them, but I won't fix that now.
*	make REPL tests look at DOTTY_EXTRA classpath entries	Martin Odersky	2016-11-24	1	-1/+3
\|
*	Make tests depend on environment variables for classpath jars	Felix Mulder	2016-11-23	1	-0/+22
	sbt adds the correct jars to classpath and the tests depend on `packageAll` which creates these. When using something else however, these together with `sbt-interfaces` do not get propagated from the build. To remedy this and make the testing a bit more flexible, we now take these from `sys.props` instead, see `tests/dotty/Jars.scala`. If the props aren't defined we fall back to the ones default to sbt.