d620e71bb6
JVM assertions have to be enabled with the -ea flag so it's possible for these checks to be ignored. |
||
|---|---|---|
| .. | ||
| avalanche | ||
| behave | ||
| corda-utils | ||
| kryo-hook | ||
| quasar-hook | ||
| sandbox | ||
| src | ||
| build.gradle | ||
| README.md | ||
Experimental module
The purpose of this module is to hold code that isn't yet ready for code review, but which still wants to be refactored and kept compiling as the underlying platform changes. Code placed into experimental must eventually either be moved into the main modules and go through code review, or be deleted.
Code placed here can be committed to directly onto master at any time as long as it doesn't break the build (no compile failures or unit test failures). Any commits here that break the build will simply be rolled back.
To help reduce the build times, unit tests for experimental projects have been disabled and will NOT run alongside
the whole project tests run via Gradle. Add parameter experimental.test.enable (example command is gradlew test -Dexperimental.test.enable
to enable those tests.