Open posix4e opened 10 years ago
I wonder if we can reduce this any more
c5db:c5-general-replication:0.1-SNAPSHOT c5db:c5db-util:tests:0.1-SNAPSHOT c5db:c5db-replicator:0.1-SNAPSHOT c5db:c5db-olog:0.1-SNAPSHOT c5db:c5-modules:tests:0.1-SNAPSHOT c5db:c5db-replicator:tests:0.1-SNAPSHOT c5db:c5-proto:0.1-SNAPSHOT io.protostuff:protostuff-api:1.1.0-SNAPSHOT io.protostuff:protostuff-core:1.1.0-SNAPSHOT org.jetbrains:annotations:13.0 org.mockito:mockito-core:1.9.0 org.objenesis:objenesis:1.0 c5db:c5-modules:0.1-SNAPSHOT c5db:c5db-protostuff-codec:0.1-SNAPSHOT io.protostuff:protostuff-runtime:1.1.0-SNAPSHOT io.protostuff:protostuff-collectionschema:1.1.0-SNAPSHOT io.protostuff:protostuff-json:1.1.0-SNAPSHOT org.slf4j:slf4j-simple:1.7.4 com.codahale.metrics:metrics-core:3.0.0 c5db:c5db-util:0.1-SNAPSHOT org.slf4j:slf4j-api:1.7.5 org.jetlang:jetlang:0.2.10
One element of how the replicator work last involves the module system as a "dial tone" of how in-process modules work.
The jetlang dependency is also firm since it provides a basis for async comms and test ability. =
Perhaps this is just a matter of documentation. Checkout https://github.com/zk1931/jzab/wiki https://github.com/zk1931/jzab/blob/master/pom.xml Has basically the same dependencies no jetlang and protobuf 2.4.1 instead of protostuff
Although we have much better test coverage, and our code is arguably easier to understand,
If a third party user wants to pull in our replicator we should have almost no dependencies.