Lorenzo Bettini Messages: 1716 Registered: July 2009 Location: Firenze, Italy
If I run the Xtend standalone compiler in the headless build (with
Buckminster), the corresponding .java._trace files contain a reference
to the original xtend file with an absolute path (starting with
file:/home/...). This happens in spite of the compiler being called
with command line argument: "-d xtend-gen src".
This way, the corresponding generated source bundles are not very
useful, since you can't inspect the source of a Java class generated
from an xtend file (Eclipse will show an empty file in the editor). Of
course you can manually open the corresponding .xtend file in the source
bundle but that's not convenient.
This does not happen if the xtend compilation takes place in the
workbench: the .java._trace files contain a reference to the original
xtend file with a relative path, and the corresponding source bundles
can be efficiently used.
I have a similar issue.
When building a maven module which uses xtext-maven-plugin for code generation the created *java._trace files contains a String like
When building it in eclipse the same *java._trace contains "com/.."
I have no idea how this trace thing works, but it seems to be the cause of my problem, that in some cases the F3 (Open Declaration) does not work.
When I debug into org.eclipse.xtext.xbase.ui.editor.XbaseResourceForEditorInputFactory.createResource(IClassFile classFile) I get an uri
"C:/../maven/../emulator.topology-0.0.10-SNAPSHOT-sources.jar!/Jenkins/workspace/emulator%20nightly%20build/emulator.topology/src/main/java/com/.." which does not exists.
I see that your issue has been solved, but I do not know what I have to do.
Could you please help me?
Thanks for your answer, yes it was a long time ago, and it took me one day to find this thread
I am using xtext 2.9.2 . The grammer was originally created with 2.8.2. (I am not sure whether the issue accorded with 2.8.2)