From 7898368fe809779e73ef1cd909f1b2e5de84e6c1 Mon Sep 17 00:00:00 2001 From: Olivier Mélois Date: Wed, 18 Apr 2018 22:36:00 +0100 Subject: Make builds able to depend on external projects (#291) * Make builds able to depend on external projects Builds are now able to load external projects and depend on them as if they were local submodules. `import $file.external.path.build` * Disambiguate "dest" for foreign modules. * Calling modules loaded from external directories "Foreign" to avoid conflicting with the already existing concept of "ExternalModule". * Amended the way `dest` is computed for foreign modules * Added tests to check that the source paths and dest are as expected * Added a test to show that local modules do not conflict with foreign modules when they are named the same * WIP windows build fail * Added bootstrapping step in CYGWIN CI job * * Revert externalOutPath deletion * Add documentation for foreign-modules * reverting appveyor changes * Disabling Foreign modules tests against Java9 See https://github.com/lihaoyi/mill/issues/302 --- build.sc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'build.sc') diff --git a/build.sc b/build.sc index b80b6c0f..e1a0ba02 100755 --- a/build.sc +++ b/build.sc @@ -80,7 +80,7 @@ object core extends MillModule { ) def ivyDeps = Agg( - ivy"com.lihaoyi:::ammonite:1.1.0-14-037b8eb", + ivy"com.lihaoyi:::ammonite:1.1.0-16-147fdfe", // Necessary so we can share the JNA classes throughout the build process ivy"net.java.dev.jna:jna:4.5.0", ivy"net.java.dev.jna:jna-platform:4.5.0" -- cgit v1.2.3