mill - Your shiny new Java/Scala build tool!

	Commit message (Collapse)	Author	Age	Files	Lines
*	rename forge -> mill	Li Haoyi	2017-11-10	2	-508/+0
\|
*	Kill `Router.main` annotation and make routing dependent on the `Command` ↵	Li Haoyi	2017-11-10	1	-2/+1
\| \| \| \|	return type
*	Migrate over to the new `Task`/`Target`/`Command` split	Li Haoyi	2017-11-09	2	-12/+12
\|
*	Swap `compileScala` over to `T{...}` macro	Li Haoyi	2017-11-08	1	-2/+0
\|
*	First full metacircular compile-build-execute workflow now works using the ↵	Li Haoyi	2017-11-07	1	-6/+13
\| \| \| \| \| \| \| \|	`build.sc` file in the root of the repo. Run using ``` sbt scalaplugin/compile "core/run build.sc ScalaPlugin.console" ```
*	- Allow main methods to return `Target[T]`s, so they can then be evaled by ↵	Li Haoyi	2017-11-07	1	-3/+4
\| \| \| \| \| \|	an external `Evaluator` that has the `Discovered` mapping available - Basic integration tests for `T.command` entrypoint running in the `JavaCompilerJarTests` suite
*	Recursive main-method resolution now works, as part of the normal discovery ↵	Li Haoyi	2017-11-05	3	-28/+53
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	recursion ```scala @ import forge.util.JsonFormatters._ import forge.util.JsonFormatters._ @ forge.discover.Discovered[forge.scalaplugin.MetacircularTests.type] @ forge.discover.Discovered[forge.scalaplugin.MetacircularTests.type].mains res2: Seq[...] = List( NestedEntry(List("ScalaPlugin"), ..., EntryPoint("run", ...)), NestedEntry(List("Core"), ..., EntryPoint("run", ...) ) @ forge.discover.Discovered[forge.scalaplugin.MetacircularTests.Core.type].mains res3: Seq[...] = List( NestedEntry(List(), ..., EntryPoint("run", ...)) ) ```
*	Forked `ammonite.main.Router` into `forge.discover.Router`, to let us ↵	Li Haoyi	2017-11-05	2	-7/+408
\| \| \| \| \| \|	generate routes purely based on a type `T`, as part of the target discovery process. We defer the need for a concrete value of type `T` later until we need to evaluate the route. Eventually this should go upstream into ammonite itself, but forking is easier for now
*	Add a simple consistency checker on `Discovered` to test if any of the ↵	Li Haoyi	2017-11-05	1	-0/+7
\| \| \| \|	observable `Target`s in the given base are not being properly cached
*	Re-organize `forge/` folder according to ordering of build phases: target ↵	Li Haoyi	2017-11-05	2	-0/+70
	definition, target discovery, and target evaluation