| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
making changes within them get picked up by the file-watching `~compile`/`~test` commands
|
|
|
|
|
|
|
|
| |
hierarchy, which each module receives and extends.
One constraint is that now must define your abstract modules as `trait`s rather than `class`es, or otherwise add an implicit `ctx: ModuleCtx` parameter to your class definition.
So far this lets us remove some explicit `basePath` definitions in `build.sc`. Proper handling of `basePath` in `CrossModule`s is future work
|
| |
|
|
|
| |
* Fix #99 - it's required to provide sbt.testing.Selector for scalatest
|
| |
|
|
|
|
| |
conventions
|
| |
|
| |
|
|
|
|
|
|
| |
sensitive to working directories
Make `run` and `runMain` take option CLI args
|
|
Those tests now download a snapshot of the relevant git repo rather than vendoring the files, and use a bare `build.sc` instead of having the build object be included in the test classpath.
Tests pass using `sbt integration/test`, but `mill integration.test` still doesn't work
|