Spurious "No builder defined for this editor"
I was working on some Spoofax projects, normally.
I shutdown my computer and later restarted.
I opened the comp.any.entities project.
I opened the example.ent file.
I clicked the Transform toolbar icon.
I got the message “No builder defined for this editor.”
As far as I know, the project was in a clean state.Same results for another sdf/stratego project, which formerly was functional.
Then I closed the comp.any.entities project.
Deleted it.
Created it new.Now the above spurious error message does not appear, in either project.
This is not a serious issue.
Submitted by lloyd konneker on 5 October 2011 at 00:22
The workaround seems to be as described above.
I am just reporting it in case someone else encounters this issue.
Issue Log
Thanks for reporting. Strange issue. What version are you using? Do you get this with a clean project created by the wizard? Are there any errors in the error log? (menu window > show view > error log)
My configuration:
AMD64
Ubuntu 10.4
Eclipse 3.5.2
Spoofax downloaded in the last month (version?)I closed all projects and closed Eclipse.
I restarted Eclipse.
I double clicked on my project to open it.
I selected my example file test/example.obp (obp is the suffix for my language.)
At that point, I got this in the error log.Warning
Wed Oct 05 11:54:21 EDT 2011
A conflict occurred for CTRL+T:
Binding(CTRL+T,
ParameterizedCommand(Command(org.strategoxt.imp.runtime.transformCommand,Transform,
Transform,
Category(org.strategoxt.imp.runtime.transformCommandCategory,Transform Command category,null,true),
ActionDelegateHandlerProxy(null,org.strategoxt.imp.runtime.services.BuilderButtonDelegate),
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.ui.textEditorScope,,,system)
Binding(CTRL+T,
ParameterizedCommand(Command(org.strategoxt.imp.runtime.transformCommand,Transform,
Transform,
Category(org.strategoxt.imp.runtime.transformCommandCategory,Transform Command category,null,true),
ActionDelegateHandlerProxy(null,org.strategoxt.imp.runtime.services.BuilderButtonDelegate),
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.ui.textEditorScope,,,system)Then the Transform button failed as described in this issue.
I assume the warning is relevant.
Maybe the accelerator key binding conflicts with other plug-ins I have installed in Eclipse (PyDev and Android.)Then I close my project and open a clean EntityLang project.
It also fails on the Transform button.Then I deleted the EntityLang project and created it anew.
The Transform button now works.
However, when I open my project (obp) the Transform button fails.
So the workaround described above is not reliable.I’ll post again if I find a reliable workaround.
More info:
On another machine:
Ubuntu 10.4 I86 32bit
PyDev Eclipse plugin is installed but not Android pluginThis issue does not exist.
Note for Eclipse users:
What files you see listed depends on the Eclipse Perspective: Java perspective works but not PyDev perspective, for Spoofax projects.
The PyDev perspective shows .java files but not .ent files or other files in your language?
I retract the previous comment. The issue still exists even without the Android plugin. I still haven’t worked out a reliable way of reproducing or working around the issue.
You installed Spoofax from the normal update site? Could you try the
http://lclnet.nl/update/unstable
update site instead to see if that fixes your issue?
OK, I did that: now using Spoofax/IMP 0.6.1.4-r23404 org.strategoxt.imp.feature.group
Issue still exists but still sporadic.
New info: in addition to the error log reported above, the original example.ent file yields a warning on the first line:
Description Resource Path Location Type
Content is not allowed in prolog. example.ent /comp.any.entities/test line 1 Ant Buildfile ProblemSo my limited understanding is that the first error is that example.ent fails to parse, and that means Spoofax can’t build a builder ( a transformer), so the error message when pulling down the Transform menu is more or less correct.
Log in to post comments