Artifacts using The Multiverse Code (so API and Implementation) (7)

The Groovy and Java high-level concurrency library offering actors, dataflow, CSP, agents, parallel collections, fork/join and more

Contains an all in one jar that that contains the AlphaStm including the Multiverse Javaagent and the Multiverse Compiler. This is the JAR you want to include in your projects, if you do, you don't need to worry about any Multiverse dependency at all.

Contains support functionality for instrumenting classes so that they can participate in stm. The actual instrumentation (that is very STM specific) is not part of this package.

Contains the main Multiverse STM Implementation: the Alpha Engine. The Alpha engine supports readonly and update transactions. It also supports the retry/or else mechanism. This not the jar you want to have in your final distribution because it isn't instrumented (hence the name unborn). The jar you eventually want to have in your distribution is the multiverse-alpha jar. What this package does, is test the instrumentation for the Javaagent. The compiletime ...

Contains the tests of core interfaces/classes of the Multiverse project. So no STM implementations. These tests are seperated from the

Scala classes to allow more elegant use of Multiverse from Scala. Atm the functionality is quite limited since not a lot of effort was put in the Scala integration. For the 0.6 release Multiverse should be able to work with in Scala written transactional objects configured with the Multiverse annotations. So that would reduce the need for this library, although in Scala they want to have special Scala 'interfaces' that provide some syntactic sugar to use java collections ...

Scala classes to allow more elegant use of Multiverse from Scala