| [Acceleo 3] Question about debugging templates [message #557523] |
Tue, 07 September 2010 19:48  |
Eclipse User |
|
|
|
Hey Obeo folks,
In past versions of Acceleo when we had runtime errors in our templates, the template editor would highlight in red the problem code. I'm just wondering if this feature is available in Acceleo 3? I didn't see it at all while debugging my code. If not, will the feature be added in the future? Without this it is much harder to find out which lines in the templates are causing problems.
Thanks for your help!
Tom G
|
|
|
|
| Re: [Acceleo 3] Question about debugging templates [message #557668 is a reply to message #557659] |
Wed, 08 September 2010 09:17  |
| Eclipse User |
|
|
|
This is a multi-part message in MIME format.
--------------040505060702060204090601
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Hi Tom,
To complete, we do not intend on reporting "runtime" errors in the
template editor itself for Acceleo 3. The console and error log display
stack traces corresponding to "in which module did the failure happen,
an on which line". We consider these stack trace to be more powerful
than a simple red marker in the editor, as it allows you to trace
exactly from which templates the call leading to a failure came.
Laurent Goubet
Obeo
Stephane Begaudeau wrote:
> Hi Tom,
>
> In Acceleo 3.0, we notify the user with marker for any error during the
> parsing (if you forget to close a block for example). Parsing problems
> are visible in the editor. We will also have warnings and informations
> (TODO / FIXME) in Acceleo 3.1
> ( http://sbegaudeau.tumblr.com/post/961722949/user-interface-i mprovements-in-acceleo-3-1).
> And during the generation, we also notify the user if something goes
> wrong, this time in the console.
>
> Do you have a specific kind of error that was detected in Acceleo 2,
> that is not detected in Acceleo 3 ?
>
> Stephane Begaudeau, Obeo
--------------040505060702060204090601
Content-Type: text/x-vcard; charset=utf-8;
name="laurent_goubet.vcf"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="laurent_goubet.vcf"
YmVnaW46dmNhcmQNCmZuOkxhdXJlbnQgR291YmV0DQpuOkdvdWJldDtMYXVy ZW50DQpvcmc6
PGEgaHJlZj0iaHR0cDovL3d3dy5vYmVvLmZyIj5PYmVvPC9hPg0KZW1haWw7 aW50ZXJuZXQ6
bGF1cmVudC5nb3ViZXRAb2Jlby5mcg0KdXJsOmh0dHA6Ly93d3cub2Jlby5m cg0KdmVyc2lv
bjoyLjENCmVuZDp2Y2FyZA0KDQo=
--------------040505060702060204090601--
|
|
|
|
Powered by
FUDForum. Page generated in 0.02870 seconds
Home