| associatedPath may not be null [message #1443382] |
Sun, 12 October 2014 16:57  |
 Owen Arden
Messages: 3
Registered: October 2014 |
Junior Member |
|
|
Hi,
I've created a subclass of JvmModelGenerator to customize the code generated for my Xtext language. However, during compilation of (apparently) any source files I get an IllegalArgumentException that says "associatedPath may not be null" from
org.eclipse.xtext.generator.trace.TraceRegion (stack trace appended below).
Comparing my code to JvmModelGenerator, I don't see what I'm doing differently, but then I don't quite understand what the assumptions of the trace API are. I've tried to figure it out, but there are in fact several places where LocationData objects are created with a null path explicitly.
Could someone give me a hint about what I may be doing wrong? Or even just a summary about how the trace API should be used? Any tips on how to figure out which calls to ITreeAppendable.trace or ITreeAppendable.append might be generating the offending regions would also be appreciated.
Thanks,
Owen
964 [Worker-2] ERROR org.eclipse.xtext.builder.trace.TraceForStorageProvider - associatedPath may not be null
java.lang.IllegalArgumentException: associatedPath may not be null
at org.eclipse.xtext.generator.trace.TraceRegion.<init>(TraceRegion.java:52)
at org.eclipse.xtext.generator.trace.TraceRegionSerializer$IdentityStrategy.createRegion(TraceRegionSerializer.java:58)
at org.eclipse.xtext.generator.trace.TraceRegionSerializer$IdentityStrategy.createRegion(TraceRegionSerializer.java:1)
at org.eclipse.xtext.generator.trace.TraceRegionSerializer.doReadFrom(TraceRegionSerializer.java:165)
at org.eclipse.xtext.generator.trace.TraceRegionSerializer.doReadFrom(TraceRegionSerializer.java:139)
at org.eclipse.xtext.generator.trace.TraceRegionSerializer.readTraceRegionFrom(TraceRegionSerializer.java:128)
at org.eclipse.xtext.builder.trace.TraceForStorageProvider$CachedTraces.getTraceRegion(TraceForStorageProvider.java:146)
at org.eclipse.xtext.builder.trace.TraceForStorageProvider$1.getTraceRegion(TraceForStorageProvider.java:174)
at org.eclipse.xtext.builder.trace.AbstractTrace.doGetRootTraceRegion(AbstractTrace.java:116)
at org.eclipse.xtext.builder.trace.AbstractTrace.getRootTraceRegion(AbstractTrace.java:108)
at org.eclipse.xtext.builder.smap.DebugSourceInstallingCompilationParticipant.findRootTraceRegion(DebugSourceInstallingCompilationParticipant.java:193)
at org.eclipse.xtext.builder.smap.DebugSourceInstallingCompilationParticipant.buildFinished(DebugSourceInstallingCompilationParticipant.java:124)
at org.eclipse.jdt.internal.core.builder.JavaBuilder.build(JavaBuilder.java:235)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:299)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:302)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:358)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:381)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
[Updated on: Sun, 12 October 2014 17:00] Report message to a moderator |
|
|
|
Powered by
FUDForum. Page generated in 0.03325 seconds
] 
Search
Help
Register
Login
Home
