A ProverException: unable to find file util.maude during backend initialization surfaces as an DescriptionFileException, see the stack trace below. I file this as a bug, since the unablity to find util.maude should not be considered to be cause by a mistake in the description file. Even if the description file has the wrong file name, there is no way to automatically decide what's wrong. So the more general ProverException should surface. Also the original message ( unable to find file util.maude) gets lost somewhere.
grape.frontend.model.DescriptionFileException: an invocation target exception occurred
at grape.frontend.model.InferenceSystem.backend(InferenceSystem.java:720)
at grape.frontend.model.InferenceSystem.fromFile(InferenceSystem.java:171)
at grape.GraPE.initialize_system(GraPE.java:152)
at grape.GraPE.new_proof(GraPE.java:673)
at grape.GraPE.main(GraPE.java:1211)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at grape.frontend.model.InferenceSystem.backend(InferenceSystem.java:696)
... 4 more
Caused by: grape.backend.ProverException: unable to find file util.maude
at grape.backend.grape2maude.GraPE2Maude.<init>(GraPE2Maude.java:81)
... 9 more
--robert
Logged In: YES
user_id=1539302
Originator: NO
Revision 68 contains a hotfix for this problem. It is not particularly elegant, but then we'll have to thoroughly rewrite all the exception handling one day, anyway (perhaps even shortly before the last black holes decay ;-); tell me what you think.