call-alloy: A simple library to call Alloy given a specification
This version is deprecated.
Please see the README on GitHub at https://github.com/marcellussiegburg/call-alloy#readme
[Skip to Readme]
Downloads
- call-alloy-0.2.0.1.tar.gz [browse] (Cabal source package)
- Package description (as included in the package)
Maintainer's Corner
For package maintainers and hackage trustees
Candidates
| Versions [RSS] | 0.1.0.0, 0.1.0.2, 0.2.0.0, 0.2.0.1, 0.2.0.3, 0.2.0.4, 0.2.0.5, 0.2.0.6, 0.2.1.0, 0.2.1.1, 0.2.2.0, 0.3, 0.3.0.1, 0.3.0.2, 0.3.0.3, 0.4, 0.4.0.1, 0.4.0.2, 0.4.0.3, 0.4.1, 0.4.1.1, 0.5, 0.5.0.1, 0.6, 0.6.0.1, 0.6.0.2, 0.6.0.3 (info) |
|---|---|
| Change log | ChangeLog.md |
| Dependencies | base (>=4.7 && <5), bytestring (>=0.10 && <0.11), containers (>=0.6 && <0.7), directory (>=1.3 && <1.4), file-embed (>=0.0.11 && <0.1), filepath (>=1.4 && <1.5), hashable (>=1.2 && <1.4), lens (>=4.17 && <4.19), mtl (>=2.2 && <2.3), process (>=1.6 && <1.7), split (>=0.2 && <0.3), trifecta (>=2 && <2.2), unix (>=2.7 && <2.8), Win32 [details] |
| License | MIT |
| Copyright | 2019 Marcellus Siegburg |
| Author | Marcellus Siegburg |
| Maintainer | marcellus.siegburg@uni-due.de |
| Category | Language |
| Home page | https://github.com/marcellussiegburg/call-alloy#readme |
| Bug tracker | https://github.com/marcellussiegburg/call-alloy/issues |
| Source repo | head: git clone https://github.com/marcellussiegburg/call-alloy |
| Uploaded | by marcellus at 2020-01-08T15:40:32Z |
| Distributions | LTSHaskell:0.6.0.3, Stackage:0.6.0.3 |
| Downloads | 5597 total (92 in the last 30 days) |
| Rating | (no votes yet) [estimated by Bayesian average] |
| Your Rating | |
| Status | Docs uploaded by user Build status unknown [no reports yet] |
Readme for call-alloy-0.2.0.1
[back to package description]call-alloy 
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.
Requriements
- 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.