| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
and add example of using akka-http that doesn’t work without this.
Also add functionality to emulate inheritIO when running via nailgun
process. Only caveat right now: user has to press ENTER to terminate
the input strea.
|
|
|
|
|
|
|
|
|
|
| |
this extracts certain parts of cbt into stand-alone libraries, which can
be published to maven and used outside of cbt.
This also adds scalariform for these parts of the code.
This slows down cbt’s own build a lot because of the number of projects
involved! So we’ll follow this by a bunch of performance tweak commits.
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Before it only affected jdk, because scala.Console captures our and err
before the swap.
This is needed when running main classes like Scaladoc or the compiler
and wanting to redirect output to standard error
|
|
|
|
|
|
|
|
|
|
| |
A SecurityManager is once installed globally and stays the same across
all classloaders. TrapSecurityManager was installed this way, but it
looked up the `trapExitCode` in it's own classloader, while
classes in other classloaders (when cbt was using another version of
cbt) were writing it to their own classloader. This flag needs to be in
a global place instead to fix this, so we'll put it straight into the
TrapSecurityManager itself.
|
|
|
|
|
|
|
|
|
| |
Installing one globally for the JVM live-time and make behavior dependent
on a thread local variable seems safer than globally switching it out
and having race conditions.
Also now all other calls are forwarded to a potential Nailgun
SecurityManager, which should fix some bugs.
|
|
|
|
| |
when CBT crashes
|
| |
|
|
|
|
|
|
|
| |
Proxy settings can be supplied either via Java system-properties or via
environment variables (http_proxy/https_proxy/no_proxy).
Java system-properties take precedence over env vars. Evaluation of
proxy settings happens only during nailgun startup for now.
|
|
|
|
| |
easier to read without.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
this showed exception when compile errors happened during Stage1.
|
|
|
|
| |
This fixes the issues with crashes loading stage2 introduces in 57de43907e05d4cd3986e2994e0e3bff93e09b4e. Also should be faster when using nailgun.
|
|
|
|
| |
(thing can still be cleaned up)
|
|
|
|
|
|
|
|
|
| |
- Changed launcher to already load zinc
- use code generation to generate necessary dependencies
- changed resolver to linearize dependency DAG in a way that guarantees that every transitive dependee of a node in the DAG is a transitive dependee of that node in the linear sequence
- move exit code trapping code into java so it can be used for zinc early
There seems to be a bug in this version, where CBT crashes about half of the time with a "object is not an instance of declaring class" Exception during running the task from the build object via reflection.
|
| |
|
| |
|
| |
|
|
|
|
| |
fix a few warnings.
|
|
|
|
|
|
| |
replace two level classloader (one for non-cachable dependencies with a cached parent one for cachable ones) with a hierachy of classloaders corresponding
this should eventually allow re-using CBT's classloader between stage1 and stage2
this change breaks the ScalaTest support for now
|
|
|
|
| |
caching classloaders hierarchically without deadlocks
|
|
|
|
| |
fragile with regards to concurrency and user code setting security managers.
|
|
|
|
| |
++ for strings everywhere. Added ++ method to File and URL and use it in many places
|
| |
|
|
|
|
| |
speed and easier transfer of part of it into java. Also enable looping to recompile NailgunLauncher and stage1
|
| |
|
|
|