Use alchemist as library in your build

Alchemist artefacts

Alchemist can be easily imported via Maven, Ivy, Gradle, or sbt

Alchemist provides artifacts on OSSRH to ease the process of being used as a library.

Easy way

Importing the it.unibo.alchemist:alchemist artifact will pull along all the simulator components, all the official incarnations, and all the required dependencies.

First, identify which version of the simulator you want to work with, this will most likely be the latest stable one. Let’s say that you picked version THE.VERSION, the following are the dependencies you want to add, depending on your build system.

Apache Maven

<dependency>
    <groupId>it.unibo.alchemist</groupId>
    <artifactId>alchemist</artifactId>
    <version>THE.VERSION</version>
</dependency>

Gradle

compile 'it.unibo.alchemist:alchemist:THE.VERSION'

Scala SBT

libraryDependencies += "it.unibo.alchemist" % "alchemist" % "THE.VERSION"

Apache Ivy

<dependency org="it.unibo.alchemist" name="alchemist" rev="THE.VERSION" />

Apache Buildr

'it.unibo.alchemist:alchemist:jar:THE.VERSION'

Groovy Grape

@Grapes(
@Grab(group='it.unibo.alchemist', module='alchemist', version='THE.VERSION')
)

Leiningen

[it.unibo.alchemist/alchemist "THE.VERSION"]

Cleaner way

It is actually unlikely that you want to use the full fledged simulator in your own project. To support the case where you want a lightweight, small dependency network in your product, the simulator is composed of multiple modular artifacts. In case you want to to depend on as less artifacts as possible, you should consider verifying which Alchemist artifacts you actually need, and pointing them directly. All the Alchemist modules (including deprecated and discontinued ones) are available here on Maven Central.