homepage: https://github.com/marcellussiegburg/call-alloy#readme
changelog-type: markdown
hash: e14eb6e8bde1cd27f4f0424d0a534fe867760dfc79f47e8ac1c0853f7bc35b70
test-bench-deps:
  bytestring: -any
  split: -any
  base: ! '>=4.7 && <5'
  hspec: -any
  call-alloy: -any
  filepath: -any
  process: -any
  hashable: -any
  file-embed: -any
  directory: -any
maintainer: marcellus.siegburg@uni-due.de
synopsis: A simple library to call Alloy given a specification
changelog: |
  # Changelog for call-alloy

  ## Unreleased changes
basic-deps:
  bytestring: -any
  split: -any
  base: ! '>=4.7 && <5'
  filepath: -any
  process: -any
  hashable: -any
  file-embed: -any
  directory: -any
all-versions:
- 0.1.0.0
author: Marcellus Siegburg
latest: 0.1.0.0
description-type: markdown
description: |
  # `call-alloy` [![Build Status](https://travis-ci.org/marcellussiegburg/call-alloy.svg?branch=master)](https://travis-ci.org/marcellussiegburg/call-alloy)

  This is a simple library to call [Alloy](http://alloytools.org) 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`](https://hackage.haskell.org/package/directory/docs/System-Directory.html#t:XdgDirectory) if the libraries exist in a current version.
  If not they are placed there together with a version identifier.
license-name: MIT

Update from Hackage at 2019-10-25T15:46:51Z
Update from Hackage at 2019-10-25T15:46:51Z
