| [jet] error reporting [message #45915] |
Mon, 19 May 2008 04:38  |
Eclipse User |
|
|
|
Hey Paul and others,
I was looking for a bug that treats "better error reporting", but didn't find
anything specific. With better error reporting I mean for example, that trying
to access an undefined variable should tell you that. The exceptions I got were
really far away from anything like "undefined variable". I don't care about
uncatched exceptions , but they should be meaningful to the developer at least.
Like this, it's somehow a pain to debug through templates. Anyway, this one was
solved fast, and it's still big fun to jet.
Felix
|
|
|
|
| Re: [jet] error reporting [message #46204 is a reply to message #46115] |
Thu, 22 May 2008 05:05  |
| Eclipse User |
|
|
|
Hi Paul,
it was my fault. I am starting to dig deeper into the eclipse technology, and
things get - not more complex - but simply there's more things to look at.:
I recently put my jet transformation to be executed inside a job, to copy the
emf codegeneration feel with a nice progress bar... there, I somehow simply lost
the IStatus that the jet transformation returns..
Thanks,
Felix
|
|
|
Powered by
FUDForum. Page generated in 0.03116 seconds
Home