corda/experimental
Katelyn Baker 913ba1d46e
NOTICK - Initial work on a non JVM (C++) serialiser (#5368)
Currently, it's more of a blob inspector than a full-blown
implementation, but this code does have the ability to understand a Corda
serialized blob and build a set of deserialisers to handle a blob. It
does this in the same way the native java implementation works by
interrogating the types (as per the definition in the envelope) and
building recursive type readers that are able to pull the relevant
information out of the byte stream.

Lots of future work to undertake, but as a starting point its a little
bit useful with the scope it could be made much more useful with some
work.
2019-08-15 21:16:20 +01:00
..
avalanche CORDA-2893, ENT-3422: Tweak JUnit 5 configurations to keep vintage engine off compile classpaths. (#5138) 2019-05-20 11:57:56 +01:00
corda-utils CORDA-2893, ENT-3422: Tweak JUnit 5 configurations to keep vintage engine off compile classpaths. (#5138) 2019-05-20 11:57:56 +01:00
cpp-serializer NOTICK - Initial work on a non JVM (C++) serialiser (#5368) 2019-08-15 21:16:20 +01:00
kryo-hook/src/main/kotlin/net/corda/kryohook Add message to uses of require(...) (#4192) 2018-11-16 17:13:55 +00:00
netparams ENT-3142: net-params signing tool: include certificate path in signature (#5165) 2019-06-21 16:39:33 +01:00
nodeinfo CORDA-2833 change parameter syntax to conform to Corda CLI guidelines (#5010) 2019-04-12 14:13:53 +01:00
quasar-hook [CORDA-1879]: Ensure Node dies on unrecoverable errors. (#4213) 2018-11-12 15:56:04 +00:00
src CORDA-2327 add attachments for missing dependencies (#4456) 2019-01-02 16:16:53 +00:00
build.gradle CORDA-2893, ENT-3422: Tweak JUnit 5 configurations to keep vintage engine off compile classpaths. (#5138) 2019-05-20 11:57:56 +01:00
README.md Disable unit test for experimental projects (#2627) 2018-02-23 20:48:39 +00:00

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.