Exception when running from outside multeval's folder

[Austin Matthews]

The latest version of multeval tries to read a file called "./constants" to determine its version number. When multeval is executed from a location other than its own folder, this file does not exist, leading to an exception and the inability to run multeval.

[Ian Johnson]

Copy or link the 'constants' file to the directory where you'd like to run multeval from.

[Jonathan E. Chen]

This is a "regression" introduced in commit cb6a52. Following an example on rgagnon.com, it is fixable by adding the following to build.xml:

  <manifest>
    <attribute name="Main-Class"
           value="multeval.MultEval"/>
    <attribute name="Implementation-Version" 
           value="${version}"/> 
  </manifest>

and then changing the following in MultEval.main():

String version = MultEval.class.getPackage().getImplementationVersion(); //loadVersion();

Finally, rebuild using ant clean && ant.

It looks like MultEval.loadVersion() is only ever called from MultEval.main(), so this should be safe to change. But I'm not very familiar with Java, so this may not be the best/cleanest way to patch this (hence no pull request)...

Edit: submitted as pull request #19

[RokoMijic]

Any progress on this?

[Ozan Caglayan]

I have a fork of this repository with a lot of fixes including this one. You can try that if you'd like:
https://github.com/ozancaglayan/multeval