aboutsummaryrefslogtreecommitdiff
path: root/plugins
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #261 from cvogt/simple-exampleJan Christopher Vogt2016-10-041-0/+5
|\ | | | | Simple example
| * readmes explaining plugin folder rolesChristopher Vogt2016-09-291-0/+5
| |
* | Sonatype release plugin (#247)Nikolay Tatarinov2016-10-036-0/+513
| |
* | upgrade scalafmt 0.3.1 -> 0.4.2; load scalafmt config from config filerockjam2016-10-022-12/+44
| |
* | fix main method signature in dotty-exampleChristopher Vogt2016-10-021-1/+1
|/
* Upgrade scalafmt 0.2.5 -> 0.3.1rockjam2016-09-192-3/+4
|
* WartRemover plugin implementation (#167)Mario Pastorelli2016-09-142-0/+60
|
* include directories from classpath in uber jar. fixes multi project jarsrockjam2016-06-241-9/+6
|
* explicitly specify jar extension, delete file before writing jar in librockjam2016-06-241-19/+9
|
* uber jar put all functions in one classrockjam2016-06-242-86/+76
|
* update uber jar PRrockjam2016-06-243-162/+55
|
* write current jdk version to MANIFEST.MFrockjam2016-06-241-5/+13
|
* uber-jar plugin implementationrockjam2016-06-244-0/+249
|
* Scalafmt plugin implementation (#156)Nikolay Tatarinov2016-06-233-5/+82
| | | | | | | | | | | | | | * scalariform: improve logging, declare tasks final * scalafmt plugin implementation * add scalafmt and scalariform plugins and examples to tests * fix logging guarded logging behaviour * add notes about formatting check to README * fix compilation error in examples
* scalariform plugin naive implementationrockjam2016-06-202-0/+71
|
* refactor/simplify scalaJs plugin and exampleChristopher Vogt2016-06-194-118/+103
| | | | | | - Restructure code as 1 library case class and 1 Build mixin trait. A library is generally easier to understand and could be re-used independently. 1 trait seems simpler than several here. - Let not the plugin create the multi-project build, but the user project manually. I think while this adds some minor code overhead it is much simpler to understand. Fewer tasks and other moving parts needed. - Remove verbose nested sbt-style folder structure. It's simpler without it :).
* add support for custom scalaJsOptionsChristopher Vogt2016-06-191-2/+7
|
* propagate trigger files to combined cross build and let js tasks depend on ↵Christopher Vogt2016-06-191-2/+9
| | | | compile. this makes `cbt loop fastOptJs` work (and depending on compile seems generally a good idea)
* use long versions of scalajs linker flags for easier understandabilityChristopher Vogt2016-06-191-4/+4
|
* fix scalajs example (broke in recent refactorings and went unchecked)Christopher Vogt2016-06-191-1/+0
|
* separate sbt layout and scalatest plugins and create a more general plugin ↵Christopher Vogt2016-06-155-34/+18
| | | | architecture
* Get rid of Build default imports to reduce noise in build files. This also ↵Christopher Vogt2016-06-152-6/+0
| | | | changes builds from using immutable.Seq to using Predef.Seq in favor of simplicity over purity. This has been discussed on gitter.
* turn Build base classes into traits for less verbosity and uniform usage ↵Christopher Vogt2016-06-154-5/+5
| | | | with any other plugin
* scalajs cross project support as pluginKatrin Shechtman2016-06-133-0/+116
|
* Making scalatest plugin work + example build folder with scalatest sample buildKatrin Shechtman2016-05-261-2/+3
|
* Convenience factory methods for ResolversChristopher Vogt2016-05-031-4/+4
|
* Reproducible builds, composing different CBT version and various improvementsChristopher Vogt2016-04-282-0/+79
One large commit, because it is was hard to do these things in isolation or to separate them now. CBT now knows how to load other versions of itself - Support for reproducible builds (!), by providing a CBT git URL and hash to tie build to - Support for composing builds using different CBT versions (!) - introduce (in compatibility/) Java interfaces all CBT versions need to stay compatible with, so they can talk to each other. And put extension methods to these interfaces in cbt package object Class loading - add some sanity checks for class loading - improve class loader invalidation to fix bugs - implement caching in Java land class loaders. In particular to prevent the system class loader to repeatedly generate ClassNotFound exceptions in each sink of the class loader DAG for non JDK classes (meaning major speed up for projects with many classes). - getting rid of transient class loader cache unifying into "persistent" one instead (which is still wrong as invalidation eventually needs to invalidate entire sub graphs of the class loading DAG, not single class loaders. Seems like we'll have to abandon the hashmap based approach and tie caching to dependency objects) Other Caching - cache dependencies extracted from xml files, which was one major time killer, but invalidate cache when cbt changed (maven dependency user facing api needs simplification now!) - memorize last successful compile time in the file system rather than memory, to guard against unnecessary recompiling even across launches (or when using cbt direct) Structural improvements - Factor out ClassLoaderCache on Java land into its own class. - Port MultiClassLoader to Java land, to better compose classloaders in NailgunLauncher. - Remove many global constants and variables (in object paths and in NailgunLauncher) and pass them through instead. Needed for composing of builds. - move more code from resolver into Lib for less entanglement with classes (needed to compatibility interfaces) and better re-usability - remove canBeCached. Everything can be cached now, but we need to be careful about correct invalidation. - remove build announcing produced jars. We can add if ever needed. - change callNullary to return exit code instead of Unit as preparation for next commit introducing "recursive" ScalaTest - Makes ScalaTest support work (still a bit too inflexible, but mostly works well)