aboutsummaryrefslogtreecommitdiff
path: root/compatibility
Commit message (Collapse)AuthorAgeFilesLines
* minor fix to error messagesChristopher Vogt2017-06-153-8/+8
|
* Unify reflectively loading builds from directories.Christopher Vogt2017-03-202-1/+6
| | | | | | | | | | THis is mostly cleanup and a little bit feature. Before it was done partially in 3 places, BuildBuild, loadRoot and GitDependency. Now DirectoryDependencies also support referencing sub-builds. Also introduce scalariform for the first few files of cbt's core code :).
* fix file watching for realChristopher Vogt2017-03-122-4/+7
| | | | | | | last file watching update didn’t work well enough. This now - rips out barbary watch service as it seems buggy crashing the jvm - make cbt exclusively write files to watch to a file - uses fswatch instead watching all files in that file
* revamp loop featureChristopher Vogt2017-03-121-0/+3
| | | | | | | | | | | | | | | | | | | | | now CBT and builds pass their file names to the current build via the context. The build then simply blocks until any file changes. Then it returns with a special exit code, which the bash script picks up and restarts CBT. Thats works well for looping over project files. It works less well for looping over builds and CBT itself. For this a build has to success once, so that the .cbt-loop.tmp file exists. Then looping works for cbt and builds, but the file list is not updated in case of compile errors, etc. Fixes - https://github.com/cvogt/cbt/issues/406 - https://github.com/cvogt/cbt/issues/405 - https://github.com/cvogt/cbt/issues/202 - https://github.com/cvogt/cbt/issues/50 - https://github.com/cvogt/cbt/issues/22 We should improve for 1.0 in https://github.com/cvogt/cbt/issues/419 to handle looping over build files and cbt itself smarter.
* allow DirectoryDependencies on BuildBuildsChristopher Vogt2017-02-181-2/+6
| | | | | | | | | this fixes a bug where finalBuild would over eagerly go down all the way down to the outermost build instead of stopping at the one requested. Now it checks the new argument and stops there. This is necessary to allow having one build depend on another build in order to embed it in a type-safe way and have access to it’s tasks.
* easier setting of projectDirectory in sub-buildsChristopher Vogt2017-02-131-1/+5
| | | | | by replacing context.projectDirectory by workingDirectory and using it as the default but allowing it to being overridden
* remove some unnecessary Context fields while we are modifying contextChristopher Vogt2017-02-132-3/+4
|
* Add support for nested builds and use it to replace cross compilationChristopher Vogt2017-02-131-1/+3
| | | | | | | | command which was previously hard-coded This will allow multi-project builds, too but we should first fix caching across instances and GitDependencies on sub-builds within other repositories.
* use unboxed primitives everywhere possible for reliable == behaviorChristopher Vogt2017-02-091-1/+1
|
* idempotent change propagationChristopher Vogt2017-02-093-7/+51
| | | | | | using lastModified instead of a non-idempotent needsUpdate flag this fixes a bug where dependees would not be rebuilt if cbt exited or was killed after dependencies were already rebuilt.
* memoize task results across classes within a single runChristopher Vogt2017-02-091-0/+1
|
* replace flawed concurrent hashmap cache with consistent replacementChristopher Vogt2017-02-011-3/+3
| | | | | | | | | | | | | | | | | | | | | | | The concurrent hashmap approach to classloader caching was flawed. Assume you have two concurrently running builds A and B and projects P2 and P3 depending on project P1. And assume a time sequence where A compiles P1, then compiles P2, then P1’s sources change, then B compiles P1, then A compiles P3. At the end P2 and P3 will have different versions of P1 as their parent classloaders. This is inconsistent. The easiest way to work around this is making sure only one thread is changing the classloader cache during it’s entire run. This would mean either no concurrency or what we have done here, which is letting threads work on a copy of the cache and replace the original cache in the end using an atomic operation. This means the thread that finishes last wins, but for caching that’s fine. Worst case some things aren’t cached in a concurrent execution. This change also means that we don’t need concurrent hashmaps for the classloader cache anymore since no two theads will access the same hashmap. We still need a concurrent hashmap for the class caches inside of the classloaders as multiple threads can access the same classloaders.
* Merge separate hashmaps for persistent cache into oneChristopher Vogt2017-02-011-3/+2
| | | | | | | This isn’t type-safe, but re-using that same hashmap for both keys and classloaders allows to reduce the number of members in Context. Also we can re-use the same hashMap for other things as well in the coming commits, e.g. timestamps.
* minor cleanups regarding ContextChristopher Vogt2016-11-131-4/+4
|
* Remove version from context, we can now use dynamic overridesChristopher Vogt2016-11-091-1/+0
|
* add context based task result cacheChristopher Vogt2016-11-081-0/+1
|
* make BuildInterfaces an abstract class so it can have default valuesChristopher Vogt2016-10-031-1/+1
| | | | | and it becomes slightly easier to maintain source compatibility between cbt versions
* minor cleanupChristopher Vogt2016-06-011-1/+0
|
* read sonatype credentials from cbt installation, not from other checked out ↵Christopher Vogt2016-05-261-0/+1
| | | | version
* Reproducible builds, composing different CBT version and various improvementsChristopher Vogt2016-04-285-0/+60
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)
generated by cgit v1.2.3 (git 2.39.1) at 2024-05-04 23:33:34 +0000