Closed miklossy closed 6 years ago
did you find out why org.eclipse.xtext.ui.generator.trace.TraceBasedOpenerContributor
does not populate the acceptor org.eclipse.xtext.ui.generator.trace.TraceBasedOpenerContributor.collectOpeners(IEclipseTrace, ITextRegion, IAcceptor<FileOpener>)
should call back the acceptor
and: if you customize the generator and dont create traces i think you should disable the creation of the trace files
p.s. i could not reproduce this in 2.14 is it possbile you have old trace files flying around
Yes, I had some obsolete trace files created by the original JvmModelGenerator.
After removing them the problem has been solved.
Thank you very much for your assistant!
@szarnekow do we consider this as a usecase where the traces should be deleted or is switching from a trace based dsl to a non trace based dsl a usecase where the dsl developer has to take care
No, I don't think this is an important case.
import org.eclipse.xtext.xbase.compiler.JvmModelGenerator import org.eclipse.emf.ecore.resource.Resource import org.eclipse.xtext.generator.IFileSystemAccess
class RuleEngineGenerator extends JvmModelGenerator {
}
class RuleEngineRuntimeModule extends AbstractRuleEngineRuntimeModule {
}