Quantcast

Groovy plugin issues

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Groovy plugin issues

Robert La Ferla
We are using: Groovy-Eclipse Feature 2.0.2.20100630-0900-e35 with Eclipse 3.5.  We found two issues with it:

1.  (SERIOUS) The plugin does not indicate whether the Groovy script has any "compile" errors.  This is a VERY serious problem because we have found that numerous errors AFTER releasing our software for testing because it's not caught by Eclipse.   Please work on fixing this as this will greatly benefit Groovy development.

2.  There is a small but annoying bug with "Organize Imports" where the plugin puts a new "import" above the "package" line.  This results in a run-time error.

Thanks
Robert

-- 
- --
Robert La Ferla
VP Engineering
OMS SafeHarbor

This message (and any attachments) contains confidential information and is protected by law.  If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, distribution, or the taking of any action based on this message, is strictly prohibited.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Groovy plugin issues

Andrew Eisenberg
Hi Robert,

> 1.  (SERIOUS) The plugin does not indicate whether the Groovy script has any
> "compile" errors.  This is a VERY serious problem because we have found that
> numerous errors AFTER releasing our software for testing because it's not
> caught by Eclipse.   Please work on fixing this as this will greatly benefit
> Groovy development.

Compile errors should be shown in the problems view and in the editor.
 This may not occur is if your groovy scripts are not on the Java
build path.  Is this the case?

There may be other reasons as well, but in my experience, this is the
most common cause of problems.

> 2.  There is a small but annoying bug with "Organize Imports" where the
> plugin puts a new "import" above the "package" line.  This results in a
> run-time error.

This problem occurs when there are syntax errors in the file,
preventing the Groovy parser from gathering any useful information
from the source code.  Some parse errors can be handled by the groovy
parsers (such as dangling '.'), but others we still have trouble with
(eg- unclosed parens).  You will need to ensure that all unhandled
parsing problems are fixed before performing organize imports.

The two problems might be related.  However, organize imports will not
work in groovy files that are outside the build path, so you may be
seeing another problem manifesting itself.  Can you possibly send over
a small, failing project that I can look at?

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Loading...