diff options
author | Li Haoyi <haoyi.sg@gmail.com> | 2017-12-06 20:53:29 -0800 |
---|---|---|
committer | Li Haoyi <haoyi.sg@gmail.com> | 2017-12-06 20:54:04 -0800 |
commit | 7239d6bd64ec0d025686f5f97aaaf94b7ab43951 (patch) | |
tree | ada5a410d1ee7d658d98e3b57e4188d013109451 /readme.md | |
parent | 7a1b339b08a7e6b99da7d98b1856d534c207c99e (diff) | |
download | mill-7239d6bd64ec0d025686f5f97aaaf94b7ab43951.tar.gz mill-7239d6bd64ec0d025686f5f97aaaf94b7ab43951.tar.bz2 mill-7239d6bd64ec0d025686f5f97aaaf94b7ab43951.zip |
Explicitly pass built compiler-bridge jar locations from the build system into Mill as JVM properties.
This makes the dependency between the compiler-bridge jar and the Mill executable explicit, allowing us to swap out the locations compiler-bridge jars (which end up in different places, depending on whether you're building with SBT or Mill) or eventually making them load from Maven Central in a "release" Mill executable
Since Mill (and uTest) both do not support SBT-style test arguments, we need to use `forkTest` instead of `test` to run the Mill tests passing the compiler-jar locations as JVM props. This necessitated some fixes to make `forkTest` behave properly
Diffstat (limited to 'readme.md')
0 files changed, 0 insertions, 0 deletions