| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |
| |
| |
| | |
now you can publish your module with `mill run MyModule.publish --credentials $SONATYPE_CREDENTIALS --gpgPassphrase $GPG_PASSPHRASE`
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Report errors when dependency resolution fails
Function `Lib.reolveDependencies` now checks the result of the coursier dependency
resolution for errors. The return value of the fuction is now a
`Result[Seq[PathRef]]` and errors are signaled by returning an instance
of Failure when errors occur while resolving dependencies.
`ScalaModule` now has a new task called `resolve` which allows for
triggering dependency resolution directly from the cmd line like:
`mill run resolve`.
`ResolveDepsTests` was added to verify failed resolution is properly
detected and reported.
* Remove type signatures in ScalaModule.scala
* Updates from PR comments
|
|/
|
|
| |
around their generated `Discovered.make` structures by hand, making it harder to accidentally generate the same `Discovered` twice and slow down runtime/compilation
|
|
|
|
|
|
|
|
| |
implementations, added a `Task.sequence` that does what `traverse` used to do
- Added a `test.sh` script to easily kick off self-hosted unit test runs
- Tweak `ScalaModule` to fall back to the old behavior of including the transitive classpath during compilation
|
|
|
|
|
|
| |
https://github.com/lihaoyi/mill/issues/59)
- Add missing flag to fix downloading of source jars for IntelliJ
|
| |
|
|
|
|
| |
Move `assembly`/`releaseAssembly` targets out of the stub `ScalaModule`, to take advantage of the new top-level `Target` support
|
| |
|
|
|
|
| |
`codeWrapper` to inherit from `mill.Module`
|
| |
|
| |
|
| |
|
|
|
|
| |
classpath of downstream modules, so they appear in downstream `assembly`s. Necessary to make `AutoOverridePlugin` work in the mill-build mill executable
|
|
|
|
|
|
|
|
| |
keyword when overriding a field within a `mill.Module`
This only applies to `mill.Module`s, not overrides elsewhere which still require the keyword. `mill.Module`s tend to have lots and lots of overriding, so the keyword is basically noise.
Also includes the necessary build changes to enable the locally-built Scalac plugin when compiling the test suite. Note that no changes are necessary for the executable assembly, because the `scalac-plugin.xml` will be included in the assembly and get picked up by the Ammonite scalac plugin classloader automatically
|
|
|
|
| |
doesn't run properly for some reason
|
| |
|
|
|
|
|
|
| |
managed by the `Evaluator`, which is now a stateful object that shouldn't be thrown away every time.
We still need to update the code/test-suite to make the `Evaluator` hang around in between `evaluate` calls
|
| |
|
|
|
|
|
|
|
|
| |
`ReplApplyHandler` keep using the same one every time to avoid busting caches due to REPL commands being added to the classpath
Reverts https://github.com/lihaoyi/mill/pull/60, which seems to break `mill.scalaplugin.AcyclicTests.scala2123` (reproducible in master)
Tweak `build.sbt` to properly set the forked test working directory in `test-only` as well as `test`
|
|\
| |
| | |
Separate module for Mill binary
|
| | |
|
|/ |
|
| |
|
|\
| |
| | |
Fix task cache in REPL
|
| | |
|
|/ |
|
|
|
|
|
|
| |
* Resolve compiler bridge jar
* Create a release artifact
|
| |
|
| |
|
|
|
|
| |
query for terms like `Core.compile`, but still can't run `Core.compile()`
|
|
|
|
|
|
| |
default source/test locations for builds using SBT project layout
Also split out plain-old-Scala-logic in `Lib` from inheritable traits in `ScalaModule`, since `ScalaModule` was getting a bit unwieldy
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
pass compile analysis of projectDeps to zinc
|
|/ |
|
| |
|
|
|
|
|
|
|
|
| |
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
|
|\ |
|
| |\ |
|
| | |
| | |
| | |
| | | |
jars get build for use by the executable
|
| | |
| | |
| | |
| | | |
ScalaInstance/Classloader instances around between compiles
|
|\ \ \
| |/ /
|/| /
| |/ |
|
| |
| |
| |
| | |
`log.outputStream`
|
| | |
|
| | |
|