When I try to resolve I get an error in the error log (and resolving fails):

java.lang.RuntimeException: java.io.FileNotFoundException: /git/mobl/stdlib
at org.strategoxt.imp.runtime.services.StrategoObserver.configureRuntime(StrategoObserver.java:628)
at org.strategoxt.imp.runtime.services.StrategoObserver.invoke(StrategoObserver.java:501)
at org.strategoxt.imp.runtime.services.StrategoObserver.invokeSilent(StrategoObserver.java:547)
at org.strategoxt.imp.runtime.services.StrategoObserver.invokeSilent(StrategoObserver.java:527)
at org.strategoxt.imp.runtime.services.StrategoReferenceResolver.getLinkText(StrategoReferenceResolver.java:82)
at org.strategoxt.imp.runtime.dynamicloading.DynamicReferenceResolver.getLinkText(DynamicReferenceResolver.java:25)
at org.strategoxt.imp.runtime.services.DocumentationProvider.getDocumentation(DocumentationProvider.java:28)
at org.strategoxt.imp.runtime.services.AnnotationHoverHelper.getHoverHelpAt(AnnotationHoverHelper.java:48)
at org.eclipse.imp.editor.internal.HoverHelpController.getHoverInfo(HoverHelpController.java:59)
at org.eclipse.jface.text.TextViewerHoverManager$4.run(TextViewerHoverManager.java:168)
Caused by: java.io.FileNotFoundException: /git/mobl/stdlib
at org.spoofax.interpreter.library.IOAgent.setWorkingDir(IOAgent.java:96)
at org.strategoxt.imp.runtime.services.StrategoObserver.configureRuntime(StrategoObserver.java:622)
… 9 more

Somehow the path gets messed up there (the /Users/zef part is missing).

This works fine in the stable version of Spoofax.

Submitted by Zef Hemel on 22 March 2011 at 20:38

Do you know the revision where this happens? And I suppose this happened for a file that you parsed with parse-file? And that you passed a relative path to parse-file? This might have something to do with the recent changes in the AbstractSGLRI class. I don’t think the current directory is considered anymore when converting a relative path to an absolute path.

I don’t know what revision, the one that’s currently on http://www.lclnet.nl/update/unstable I suppose. And yes, it is likely that this occurs when using parse-file, and I would not be at all surprised if this path is relative.

Oh. So that should be r22364. Could you try the latest nightly release instead? Maartje fixed some issues related to this stuff in more recent revisions. (I’m not sure if it takes the current directory into consideration though…)

Yes, it’s fixed in this version. Cool! When can we expect a (at least unstable) build?

Ok, closing this issue. Would you need a new unstable build? We’re mostly relying on the nightlies now, unstable is just not updated as often anymore.