mill - Your shiny new Java/Scala build tool!

	Commit message (Collapse)	Author	Age	Files	Lines
*	collapse boilerplate folder structure within src/ folders (#505)	Li Haoyi	2018-12-12	1	-164/+0
\| \| \| \| \| \|	* collapse boilerplate folder structure within src/ folders * .
*	First pass at splitting out worker-api from mill core. (#504)	Li Haoyi	2018-12-12	1	-1/+1
\| \| \| \| \| \| \| \| \|	This reduces the {scala,scalajs,scalanative}-worker dependency from the entirety of Mill to a much narrower `mill.api` module. This reduces the amount of classpath pollution within these workers, should mean they're much faster to download the first time, and reduces the amount of random junk they would pull in if they were to be used outside of the Mill project. The interactions between the various Modules and their WorkerImpls has been narrowed down to the `.api` modules, which only depend on other `.api` modules. A lot of things have been moved around; user code is unlikely to break, but it's possible some will if it references classes that have been moved around. Forwarders have been left for the few internal classes that Mill uses in it's own `build.sc`, to support bootstrapping. Third-party code which breaks should be a straightforward to fix just by updating imports The `*.api` modules have minimal dependencies (mostly uPickle and os-lib) and minimal code. There is still a bunch of implementation code in there: some of it defining data-types that are commonly sent across the module/worker interface (`Agg`, `PathRef`, ...), and some of it just general helper functions that are needed both in modules and workers. The latter code isn't strictly API definitions, but for now is small enough it's not worth splitting into it's own module
*	WIP migrating over from `ammonite.ops` to `os` module.	Li Haoyi	2018-11-05	1	-9/+9
\| \| \| \|	__.compile works, haven't run tests yet
*	Solves #345 : optional signing (#346)	Olivier Mélois	2018-05-23	1	-6/+12
\| \| \| \| \| \| \| \| \| \| \|	* Solves 345 : optional signing * Made gpgPassphrase optional for publishing * Added a flag to remove signing of published artifacts altogether * Handle optional value using null as default param better than using empty string as default param.
*	Re-order `gpg` signing flags to make passphrase-passing-in work	Li Haoyi	2018-04-10	1	-1/+1
\| \| \| \|	Somehow passing in `--batch` and `--passphrase` must come before the other random bits of alphabet soup
*	Better error messages when publishing to Sonatype (#138)	Andrew Richards	2018-02-19	1	-1/+1
\|
*	Allow publishing to sonatype without immediate release	Li Haoyi	2018-02-09	1	-16/+19
\|
*	Properly include the base path of the publish-destination URLs0.0.7	Li Haoyi	2018-02-04	1	-6/+9
\|
*	Fix github release creation, add new batch publishing capability to try and ↵0.0.5	Li Haoyi	2018-02-04	1	-43/+47
\| \| \| \|	speed up publishing lots of modules
*	Remove the default `publishVersion` from `PublishModule`, and add `--batch` ↵	Li Haoyi	2018-02-04	1	-1/+1
\| \| \| \|	to gpg shellout to avoid popping up a password screen
*	Swap over to simplified Mill module/source layout from SBT's	Li Haoyi	2018-01-20	1	-0/+148
	Removes a lot of useless folders and gives us a chance to exercise this simplified layout. Support for the SBT layout is still verified by our integration tests