-
-
Notifications
You must be signed in to change notification settings - Fork 360
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add exclusions and custom configuration to dependencies #254
Conversation
@shengc can we have a unit test for this? |
@lihaoyi sure, I have to do this after hours. Is the unit test supposed to be under |
@shengc probably one unit test in https://github.com/lihaoyi/mill/tree/master/scalalib/test/src/mill/scalalib to test that resolving does the right thing and the classpath is properly missing the jar that got excluded |
@lihaoyi tests are in. |
Looks good to me, thanks! |
* fix build * Detect sh/batch launcher, dev.assembly, and release filename. * Updated appveyor cache. * Added some entries for master in readme.md changelog. * Updated readme.md changelog. * fixes #173; use default(compile) configuration for deps as default (#270) * revert #254 to fix bootstrapping #268 * Updated ci tests. * Reverted Ammonite caching workaround (a796f0a) now that it's fixed * Changed ci/test-mill-0.sh to use interactive mode due to intermittent client failures to connect to server in travis * Added ci/test-mill-bootstrap.sh (ci/test-mill-0.sh with bootstrapping) and use it on oraclejdk9 instead of ci/test-mill-0.sh * Upgraded mill used for ci to 0.1.7-29-f5097f * revive #254 and fix #268 (#274) * Test mill batch (.bat) in AppVeyor * fix minor typos in docs * Sync Ammonite in ScalaModule (with build.sc).
partly borrow the idea from #214, but also reflect the exclusions in ivy and pom generation.