AlloyTools / org.alloytools.alloy, Hacker News

Alloy 4 is a self-contained executable, which includes the Kodkod model finder and a variety of SAT solvers, as well as the standard Alloy library and a collection of tutorial examples. The same jar file can be incorporated into other applications to use Alloy as an API, and includes the source code. See the release notes for details of new features.

More documentation can be found at:http://alloytools.org/documentation.html.

Alloy runs on all operating systems with a recent JVM (Java 6 or later). It is made available as a runnable jar file with both a cross-platform SAT solver (Sat4jand more efficient native SAT solvers (minisat,lingeling / plingeling,glucose).

Note however that starting with macOS High Sierra, it is necessary to install a dedicated JVM to run Alloy on macOS. A.pkgfile is provided for that purpose.

Checkout the project and type ./gradlew. You find the executable JAR in org.alloytools.alloy.dist / target / org.alloytools.alloy.dist.jar after the build has finished.

$ java version # requires 1.8 (and NOT 1.9, gradle does not run on 1.9)  java version "1.8.0 _ 144 "  Java (TM) SE Runtime Environment (build 1.8.0 _ 144 - B 01)  Java HotSpot (TM) 64 - Bit Server VM (build 25. 144 - b 01, mixed model  $ git clone [email protected]: AlloyTools / org.alloytools.alloy.git  $ cd org.alloytools.alloy  $ ./gradlew build  $ java -jar org.alloytools.alloy.dist / target / org.alloytools.alloy.dist.jar  # opens GUI

Note: if you are behind a proxy, the call togradlewis likely to fail, unless you pass it further options about the http and https proxies (and possibly your login and password on this proxy). There are several ways to pass these options, a simple one is to type (replace theXXXXX‘s by the adequate settings):

$ ./gradlew -Dhttps.proxyHost=XXXXX -Dhttp.proxyHost=XXXXX -Dhttp.proxyPort=XXXXX        -Dhttps.proxyPort=XXXXX -Dhttp.proxyUser=XXXXX -Dhttp.proxyPassword=XXXXX        -Dhttps.proxyUser=XXXXX -Dhttps.proxyPassword=XXXXX        build

Building Alloy

The Alloy build is using abnd workspacesetup using a maven layout. This means it can be build with Gradle and the Eclipse IDE for interactive development. Projects are setup to continuously deliver the executable.

Projects

The workspace is divided into a number of projects:

cnf– Setup directory. Dependencies are specified in [cnf/central.xml] using the maven POM layout
org.alloytools.alloy.application– Main application code includes the parser, ast, visualiser, and application code
org.alloytools.alloy.dist– Project to create the distribution executable JAR
org.alloytools.alloy.extra– Models and examples
org.alloytools.kodkod.core– Kodkod without native code
org.alloytools.kodkod.native– The native code libraries for kodkod

Relevant Project files

This workspace uses bnd. This means that the following have special meaning:

cnf / build.xml– Settings shared between projects
./ bnd.bnd – Settings for a project. This file willdragin code in a JAR.
(cnf / central.xml) – Dependencies from maven central

Eclipse

The workspace is setup for interactive development in Eclipse with the Bndtools plugin. DownloadEclipseand install it. You can thenImportexisting projects from the Git workspace. You should be asked to install Bndtools from the market place. You can also install Bndtools directly from theEclipse Marketplace (see (Help / Marketplace) and search forBndtools).

Bndtools will continuously create the final executable. The projects are setup to automatically update when a downstream project changes.

IntelliJ IDEA (Ultimate Edition only)

Ensure you have theOsmorcplugin is enabled, as this plugin is needed for Bndtools support. It should be enabled by default.

Choose “Import Project”
Select theorg.alloytools.alloydirectory.
Choose “Import project from external model: Bnd / Bndtools “and click” Next “
For “Select Bnd / Bndtools project to import”, all projects should be checked by default, click “Next”
For project SDK, Choose “1.8”, Click Finish

Note: donotlink the Gradle project, as this will prevent you from running Alloy within IDEA.

To run the Alloy GUI within IDEA, navigate to org.alloytools.alloy.application / src / main / java / edu / mit / csail / sdg / alloy4whole / SimpleGUI and run the SimpleGUI class.

Gradle

In the root of this workspace type./ gradlew. This is a script that will download the correct version of gradle and run the build scripts. For settings look at [gradle.properties] and [settings.gradle].

Continuous Integration

The workspace is setup to build after every commit using Travis. It releases snapshots tohttps://oss.sonatype.org/content/repositories/snapshots/org/alloytools/for every CI build on Travis.

Building the DMG file for OSX systems

Currently only the executable jar in org.alloytools.alloy.dist / target / org.alloytools.alloy.dist.jar is build. In theorg.alloytools.alloy.distproject, run../ gradlew macos. This will leave the PKG file intarget / bundle.