call-alloy: A simple library to call Alloy given a specification

[ language, library, mit ] [ Propose Tags ]

Please see the README on GitHub at

[Skip to Readme]
Versions [faq],,,,,,
Change log
Dependencies base (>=4.7 && <5), bytestring (==0.10.*), containers (==0.6.*), directory (==1.3.*), file-embed (>=0.0.11 && <0.1), filepath (==1.4.*), hashable (>=1.2 && <1.4), lens (>=4.17 && <4.20), mtl (==2.2.*), process (==1.6.*), split (==0.2.*), trifecta (>=2 && <2.2), unix (==2.7.*), Win32 [details]
License MIT
Copyright 2019 Marcellus Siegburg
Author Marcellus Siegburg
Category Language
Home page
Bug tracker
Source repo head: git clone
Uploaded by marcellus at 2020-07-09T19:12:45Z
Distributions NixOS:
Downloads 1495 total (19 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Hackage Matrix CI
Docs uploaded by user
Build status unknown [no reports yet]


[Index] [Quick Jump]


Maintainer's Corner

For package maintainers and hackage trustees

Readme for call-alloy-

[back to package description]

call-alloy Build Status

This is a simple library to call Alloy given a specification. This package includes a simple Java Library to make an API call to the Alloy Library. Alloy is included (as JAR file) within this library as well.


  • Java Runtime Environment: There is currently no warning if you have not set up any Java Runtime Environment. However, you will get runtime errors if it is not availible when a call to Alloy happens. If you want to force a check, perform the test cases.

Please note

The Java interface to get Alloy instances as well as the Alloy Jar file are backed into this library.

On every call the application checks the XdgDirectory if the libraries exist in a current version. If not they are placed there together with a version identifier.