Maybe there is one bug for groovy and one for groovy-eclipse as well (adding groovy-eclipse mail-id here so we can get some feedback from there as well)
-- Roshan Groovy Project Despot http://roshandawrani.wordpress.com/ http://twitter.com/roshandawrani On Wed, Oct 20, 2010 at 8:07 PM, David Durham <[hidden email]> wrote: That's not the exception I see in groovy-eclipse, I see all of these, |
In groovy-eclipse, I am not seeing the specific problems that you are
showing, but in the error log, I do see the stack trace that Roshan mentions. This looks like the groovy compiler crashed on this code and therefore the problems markers are not being properly created. I created: http://jira.codehaus.org/browse/GRECLIPSE-859 The Groovy-Eclipse solution may be to just pick up the groovy fix, but there might be something else going on. On Wed, Oct 20, 2010 at 7:43 AM, Roshan Dawrani <[hidden email]> wrote: > Maybe there is one bug for groovy and one for groovy-eclipse as well (adding > groovy-eclipse mail-id here so we can get some feedback from there as well) > > -- > Roshan > Groovy Project Despot > http://roshandawrani.wordpress.com/ > http://twitter.com/roshandawrani > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
Free forum by Nabble | Edit this page |