Community
Participate
Working Groups
Build Identifier: 20100617-1415 Sometimes, there is no possibility to debug the code. Therefore, it would be great to have a more informative stack trace indicating in what line from which file the execution resulted in an error. This would help immensly. Reproducible: Always
Hi Simon, We already provide stack traces relative to the Acceleo templates. Did you stumble on an exception were we do not? Could you elaborate on the type of error for which we should provide more informative stack traces?
Created attachment 179367 [details] Exception log Exception log which shows that no line number is shown during execution. However, this looks like it is a duplication of bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=290532
Simon, The exception itself is a duplicate ... but what you want isn't. We provide "custom" exceptions with template-relative stack traces when the issue is "expected" : an Acceleo "for" loop with nothing to iterate over, an Acceleo "if" with a condition which is not a boolean ... Yet when something unexpected comes up (such as a NullPointerException), we simply log the exception as it is without altering its stack trace to make it more "user-friendly". This is an enhancement that could be made rather easily, I believe it will show up in the Indigo M3 (3.1.0M3) build due the ninth of November.
From 3.1.0M5 onward, RuntimeExceptions halting the evaluation of Acceleo modules are wrapped in custom exceptions providing both the "Acceleo specific" trace and the "Standard Java" trace.
