| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
* Remove duplication from ClassLoader.create
* Prevent closing of context class loader in tests so that shutdown hooks can run
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(#414)
* Upgrade ammonite to 1.1.2-30-53edc31
This is mainly to get https://github.com/lihaoyi/Ammonite/pull/851 which
should reduce the amount of unnecessary work done by incremental
compilation in the Mill build. This requires some code changes since
this means we now depend on a more recent version of coursier, as a
side-effect this means that we do not depend on scalaz anymore.
Also use the same ammonite version in the Mill build and in
ScalaModule#ammoniteReplClasspath.
Also remove an incorrect dependency in the caffeine integration test.
This was always wrong but did not start failing until this commit,
probably due to dependencies appearing in a different order on the
classpath.
* Rename ScalaWorker to ZincWorker
Starting with the next commit, it will be used in Java-only projects
too, so the name is misleading.
* Upgrade to Zinc 1.2.1
* Fix incremental compilation when a Scala project depends on a Java project
Before this commit, JavaModule#compile simply called javac
unconditionally, thus generating new classfiles every time. But if a
Scala project depends on a Java project, this will throw off the
incremental compilation algorithm which will unnecessarily recompile
files. To avoid this we now use Zinc to compile Java projects too (as a
bonus this means that Java compilation becomes incremental). This
required some refactoring in ZincWorkerImpl to be able to compile stuff
without having to pass Scala-specific options.
The issue solved by this commit could be reproduced by running in the
Mill repository:
$ mill main.compile
$ mill -i
@ main.compile()
and observing that before this commit, the `main.compile()` call ended
up recompiling code.
|
|
|
|
| |
This makes it easier to hack on Mill using Mill itself, the evaluator is
available using `replApplyHandler.evaluator`
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Make necessary import changes
* Refactor to allow calling internally w/o println
* Refactor to allow multiple visualize modes
* Add new visualizaPlan grap entire plan
* Remove and alphabetize imports
* Document visualizePlan
|
| |
|
|
|
|
| |
in the background that only die when the task is re-run
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Allow bacticked tasks
* Prevent stack overflow
* Test for illegal bacticked identifiers
* Filter out illegal backticked identifiers
The only legal identifiers are aplanumeric, unserscore (_), and
hyphens (-).
* Remove unused method that is invalid
* Document valid characters for module/task names
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* fix #233 add append and exclude rules to assembly
* handle existing files and concatenation when file already exists in assembly
* add assembly tests for append rules
* tests for append patterns
* tests for exclude patterns
* make append algorithm use single map with fold over classpathIterator
* move assembly rules logic to method
* move grouping method to Assembly object, make assemblyRules Seq[_] rather than T[Seq[_]]
* add test cases for when there are no rules
* keep default parameter in createAssembly not to break CI
* add one more reference.conf entry to tests
|
|
|
|
| |
limitation
|
|
|
|
| |
wasn't getting picked up in the build discovery before
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Transitive reduction of visualized graph via jgrapht now works
```
out/dev/launcher/dest/run -i visualize __.compile _
out/dev/launcher/dest/run -i visualize core.__
```
* Move test running logic from scalaworker into scalalib
This is to try and reduce the size of the classpath we are passing to the test runner subprocess, in an attempt to fix the command-line-too-long errors we're getting in Appveyor. Now the test runner subprocess should no longer need Zinc or all of it's transitive dependencies
* - Break out `GraphvizTools` into a separate Mill module, to avoid bloating the main jar and try to shorten the `MILL_SCALA_WORKER` classpath being sent to scalajslib.test (which is blowing up on windows as the CLI command is too long)
- Move the meat of `resolveDependencies` from `scalalib` to `main`, to support resolving mill modules
- DRY up resolution of mill modules in `Util.millProjectModule`
* fix mill module resolution
* Tweaks to try and make zinc work again...
* Tweak `Module#reflect` to try and make it happy with `visualize` module...
* fix integration test classpath
* move visualization into it's own module
|
| |
|
|
|
|
| |
to make sure it works
|
| |
|
| |
|
|
|
|
| |
We were incorrectly duplicating the JDK classpath as part of the application classpath when we spawned the Mill server from the Mill client. This makes the transmission of application classpath to the Mill server explicit via an environment variable, so we don't end up including random things from the client classloader hierarchy that we didn't expect
|
|
|
|
|
|
|
|
| |
* wip
* Clean up more resources in the Mill client after every command
* catch and ignore SIGINT in Mill server to make it survive Ctrl-C on the client
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Adding clean as a default task
* [WIP] Improve 'clean' paths resolution
* Improve clean targets resolution mechanism
* fix error on clean all
* update "clean all" to keep all 'out/mill-*' paths
* fix cross module resolution in clean task
* Add documentation for "clean" task
|
|
|
|
| |
user to run basic mill commands (#307)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 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
|
| |
|
| |
|
|
|
|
|
| |
- Unit tests for client code using the new Java support
- Make server auto-shutdown when the client version changes, to avoid stale-server confusion
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since Mill now executes in a long-lived JVM, the builds do not have a
chance to use environment variables as inputs. This propagates the
environment variables from the client all the way down to the context
available to the tasks as a `Map[String, String]` so that they can be
used as inputs should the user choose to do so.
https://github.com/lihaoyi/mill/issues/257
|
|\ \ |
|
| | |
| | |
| | |
| | | |
- Make `Evaluator` robust against `null` results
|
| | | |
|
|/ / |
|
| | |
|
|/ |
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* fix class loading for inprocess in java 9
* always add rt jar in case of java 9
* move all custom classloading logic into mill.util.ClassLoader
* add comments explaining parent class loader changes and comment in tests pointing to original issue
|
| | |
|
|/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Upgraded Ammonite to 1.0.5-7-f032887 that includes a Java 9 performance optimization for mill's client-server mode (lihaoyi/Ammonite#773).
* Java 9 optimization for interactive mode by caching rt.jar.
* Refactored based on @lihaoyi's comments on #239.
* Removed client side rt.jar caching.
* Propagatio of home path from Cli.
* Propagation, propagation, propagation!
|
| |
|
|
|
|
|
|
|
|
|
| |
file permission (#228)
* Added support for non-interactive (client/server) mode on Windows
* Fixed assembly URI path
* Skip setting posix file permission on Windows
|
|
|
| |
Fixes #161
|
|
|
|
|
|
|
|
|
|
| |
9 (#217)
* Append "exported rt.jar" when creating URLClassLoader.
* Disabled tests involving Scala 2.10 & 2.11 and nashorn.
* Use java.net.URLClassLoader.
|
| |
|
|
|
|
|
| |
- Add a bunch of scaladoc for built in tasks
- Make `plan`, `path` etc. return a value that can JSON-serialized and displayed using `show`
|
|
|
|
| |
execution plan of running the `foo.bar` task looks like without actually evaluating it.
|
|
|
|
| |
Also re-write `Jvm.createAssembly` to allow incremental assembly construction. This should allow much faster assembly creation in the common case where upstream dependencies do not change
|
|
|
|
|
|
| |
This helps us avoid accidentally depending on the Scala library, whose classloading takes tens to hundreds of milliseconds.
This removes the last parts of the Scala library used in the client (e.g. lambdas) and reduces `mill show core.compile` from ~380ms to ~290ms
|