GRECLIPSE

Update the JDT Patch for Indigo SR1 (3.7.1)

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.5.1Release, 2.5.2.Release
  • Fix Version/s: 2.5.2.Release
  • Component/s: Editor
  • Labels:
    None
  • Environment:
    Indigo SR1 RC1, Snow Leopard 10.6.6, Java 1.6.0_26
  • Number of attachments :
    2

Description

I've been trying to use GREclipse with no success on an Indigo installation. I've tried with today's (2011/09/14) development snapshot as well as with lastest release version. Also I've tried with 1.7 and 1.8 compilers, always with the same errors.

Anytime I try to create a new class, I get this error:

"Creation of element failed.

org.eclipse.jdt.internal.core.CompilationUnit cannot be cast to org.codehaus.jdt.groovy.model.GroovyCompilationUnit".

I've attached the full exception on eclipse log (ex1.txt)

Anyway, the class is created. But anytime I double click on it, I get the following response (similar to bug https://jira.codehaus.org/browse/GRECLIPSE-1177, but not the same)

"An error has occurred. See error log for more details.
org/codehaus/groovy/eclipse/refactoring/formatter/GroovyIndentationService"

When I check the log, I see the exception I've attached on ex2.txt.

Hope this helps!

  1. Text File
    ex1.txt
    14/Sep/11 8:38 AM
    5 kB
    聲gel Eduardo Garc燰
  2. Text File
    ex2.txt
    14/Sep/11 8:38 AM
    18 kB
    聲gel Eduardo Garc燰

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Andrew Eisenberg added a comment -

It looks like the JDT patch has not been installed properly. There are several reasons for this. The most likely possibility is that you have installed Eclipse into a read-only location. In order for Eclipse to install Groovy-Eclipse's JDT patch, the install location must be writable by the current user.

If this isn't the cause, then there are some other possibilities that that might be causing this.

Show
Andrew Eisenberg added a comment - It looks like the JDT patch has not been installed properly. There are several reasons for this. The most likely possibility is that you have installed Eclipse into a read-only location. In order for Eclipse to install Groovy-Eclipse's JDT patch, the install location must be writable by the current user. If this isn't the cause, then there are some other possibilities that that might be causing this.
Hide
Permalink
聲gel Eduardo Garc燰 added a comment - - edited

I see the following on my list of installed plugins:

Groovy Compiler 1.8 Feature 2.5.2.xx-20110912-2200-e37 org.codehaus.groovy18.feature.feature.group Codehaus.org
Groovy-Eclipse Feature 2.5.2.xx-20110912-2200-e37 org.codehaus.groovy.eclipse.feature.feature.group Codehaus.org
Groovy Compiler 1.7.10 Feature 2.5.2.xx-20110912-2200-e37 org.codehaus.groovy17.feature.feature.group Codehaus.org
Groovy-Eclipse Headless Feature 2.5.2.xx-20110912-2200-e37 org.codehaus.groovy.headless.feature.feature.group Codehaus.org
JDT Core patch for Groovy-Eclipse plugin 2.5.2.xx-20110912-2200-e37 org.codehaus.groovy.jdt.patch.feature.group Codehaus.orghaus.org

The "JDT Core patch" icon has a red plus sign, don't know if that means it's not installed (it also appeared in the Install new software page). I've tried with Helios and there is no red plus sign in the icon.

Show
聲gel Eduardo Garc燰 added a comment - - edited I see the following on my list of installed plugins: Groovy Compiler 1.8 Feature 2.5.2.xx-20110912-2200-e37 org.codehaus.groovy18.feature.feature.group Codehaus.org Groovy-Eclipse Feature 2.5.2.xx-20110912-2200-e37 org.codehaus.groovy.eclipse.feature.feature.group Codehaus.org Groovy Compiler 1.7.10 Feature 2.5.2.xx-20110912-2200-e37 org.codehaus.groovy17.feature.feature.group Codehaus.org Groovy-Eclipse Headless Feature 2.5.2.xx-20110912-2200-e37 org.codehaus.groovy.headless.feature.feature.group Codehaus.org JDT Core patch for Groovy-Eclipse plugin 2.5.2.xx-20110912-2200-e37 org.codehaus.groovy.jdt.patch.feature.group Codehaus.orghaus.org The "JDT Core patch" icon has a red plus sign, don't know if that means it's not installed (it also appeared in the Install new software page). I've tried with Helios and there is no red plus sign in the icon.
Hide
Permalink
Andrew Eisenberg added a comment -

What is the filesystem location of your installation? What operating system/version are you using? Do you have write access in that location?

Installing Groovy-Eclipse into C:\Program Files on Windows 7 does not work.

Show
Andrew Eisenberg added a comment - What is the filesystem location of your installation? What operating system/version are you using? Do you have write access in that location? Installing Groovy-Eclipse into C:\Program Files on Windows 7 does not work.
Hide
Permalink
聲gel Eduardo Garc燰 added a comment -

Sorry for the late comment. I'm not getting any email every time you reply :S

As I stated in the Environment up there, I'm using Indigo SR1 RC1, Snow Leopard 10.6.6, Java 1.6.0_26. Location is totally writable. I don't know if in Mac spaces are a problem, but anyway, no spaces in the full path: /Users/MyUser/Development/eclipse-indigo-sr1-rc1. Lot's of plugins have been installed without problem.

I've also installed AspectJ compiler, and Scala Plugin, don't know if those two can cause any problem (but I have a working Helios installation with AspectJ compiler installed alongside, and it's working fine)

Show
聲gel Eduardo Garc燰 added a comment - Sorry for the late comment. I'm not getting any email every time you reply :S As I stated in the Environment up there, I'm using Indigo SR1 RC1, Snow Leopard 10.6.6, Java 1.6.0_26. Location is totally writable. I don't know if in Mac spaces are a problem, but anyway, no spaces in the full path: /Users/MyUser/Development/eclipse-indigo-sr1-rc1. Lot's of plugins have been installed without problem. I've also installed AspectJ compiler, and Scala Plugin, don't know if those two can cause any problem (but I have a working Helios installation with AspectJ compiler installed alongside, and it's working fine)
Hide
Permalink
Andrew Eisenberg added a comment -

Ahhh...I missed that the first time. Groovy-Eclipse is not yet compatible with 3.7.1 (it is not officially out yet and we have to rework our patch to be based off of 3.7.1 instead of 3.7.0). We will be making the new patch available in the next week or so.

Show
Andrew Eisenberg added a comment - Ahhh...I missed that the first time. Groovy-Eclipse is not yet compatible with 3.7.1 (it is not officially out yet and we have to rework our patch to be based off of 3.7.1 instead of 3.7.0). We will be making the new patch available in the next week or so.
Hide
Permalink
Andrew Eisenberg added a comment -

I updated the issue's title to more appropriately reflect the task that we need to accomplish.

Show
Andrew Eisenberg added a comment - I updated the issue's title to more appropriately reflect the task that we need to accomplish.
Hide
Permalink
聲gel Eduardo Garc燰 added a comment -

Ahh... I see, sorry for the confusion. I'll be making noise again in a few weeks, then .

Show
聲gel Eduardo Garc燰 added a comment - Ahh... I see, sorry for the confusion. I'll be making noise again in a few weeks, then .
Hide
Permalink
Andrew Eisenberg added a comment -

I or someone else will comment on this issue when the patch is available for 3.7.1.

Show
Andrew Eisenberg added a comment - I or someone else will comment on this issue when the patch is available for 3.7.1.
Hide
Permalink
Andrew Eisenberg added a comment -

The patch for 3.7.1 is now available.

Show
Andrew Eisenberg added a comment - The patch for 3.7.1 is now available.
Hide
Permalink
Simon McClenahan added a comment -

I'm getting the same error when I try top open a groovy file.

eclipse.buildId=M20110909-1335
java.version=1.7.0_147-icedtea
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product

Groovy-Eclipse Feature 2.6.0.xx-20111207-0900-e36 org.codehaus.groovy.eclipse.feature.feature.group Codehaus.org
Groovy Compiler 1.7.10 Feature 2.6.0.xx-20111207-0900-e36 org.codehaus.groovy17.feature.feature.group Codehaus.org
Groovy-Eclipse Headless Feature 2.6.0.xx-20111207-0900-e36 org.codehaus.groovy.headless.feature.feature.group Codehaus.org
JDT Core patch for Groovy-Eclipse plugin 2.6.0.xx-20111207-0900-e36 org.codehaus.groovy.jdt.patch.feature.group Codehaus.org

Show
Simon McClenahan added a comment - I'm getting the same error when I try top open a groovy file. eclipse.buildId=M20110909-1335 java.version=1.7.0_147-icedtea java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product Groovy-Eclipse Feature 2.6.0.xx-20111207-0900-e36 org.codehaus.groovy.eclipse.feature.feature.group Codehaus.org Groovy Compiler 1.7.10 Feature 2.6.0.xx-20111207-0900-e36 org.codehaus.groovy17.feature.feature.group Codehaus.org Groovy-Eclipse Headless Feature 2.6.0.xx-20111207-0900-e36 org.codehaus.groovy.headless.feature.feature.group Codehaus.org JDT Core patch for Groovy-Eclipse plugin 2.6.0.xx-20111207-0900-e36 org.codehaus.groovy.jdt.patch.feature.group Codehaus.org
Hide
Permalink
Andrew Eisenberg added a comment -

You are using Eclipse 3.6. Eclipse 3.6 does not support Java 7. You must upgrade to Eclipse 3.7.

Show
Andrew Eisenberg added a comment - You are using Eclipse 3.6. Eclipse 3.6 does not support Java 7. You must upgrade to Eclipse 3.7.
Hide
Permalink
Simon McClenahan added a comment -

I am using 3.7/Indigo. I don't know why the features reference e36, maybe because I'm using Groovy 1.7?

Anyway the problem has just now seemed to be resolved when I did an Eclipse update, now referencing e37.

Groovy-Eclipse Feature 2.6.0.xx-20111211-1800-e37 org.codehaus.groovy.eclipse.feature.feature.group Codehaus.org
Groovy Compiler 1.7.10 Feature 2.6.0.xx-20111211-1800-e37 org.codehaus.groovy17.feature.feature.group Codehaus.org
Groovy-Eclipse Headless Feature 2.6.0.xx-20111211-1800-e37 org.codehaus.groovy.headless.feature.feature.group Codehaus.org
JDT Core patch for Groovy-Eclipse plugin 2.6.0.xx-20111211-1800-e37 org.codehaus.groovy.jdt.patch.feature.group Codehaus.org
Eclipse Java Development Tools 3.7.1.r371_v20110810-0800-7z8gFcoFMLfTabvKsR5Qm9rBGEBK org.eclipse.jdt.feature.group Eclipse.org

Show
Simon McClenahan added a comment - I am using 3.7/Indigo. I don't know why the features reference e36, maybe because I'm using Groovy 1.7? Anyway the problem has just now seemed to be resolved when I did an Eclipse update, now referencing e37. Groovy-Eclipse Feature 2.6.0.xx-20111211-1800-e37 org.codehaus.groovy.eclipse.feature.feature.group Codehaus.org Groovy Compiler 1.7.10 Feature 2.6.0.xx-20111211-1800-e37 org.codehaus.groovy17.feature.feature.group Codehaus.org Groovy-Eclipse Headless Feature 2.6.0.xx-20111211-1800-e37 org.codehaus.groovy.headless.feature.feature.group Codehaus.org JDT Core patch for Groovy-Eclipse plugin 2.6.0.xx-20111211-1800-e37 org.codehaus.groovy.jdt.patch.feature.group Codehaus.org Eclipse Java Development Tools 3.7.1.r371_v20110810-0800-7z8gFcoFMLfTabvKsR5Qm9rBGEBK org.eclipse.jdt.feature.group Eclipse.org

People

  • Assignee:
    Andrew Eisenberg
    Reporter:
    聲gel Eduardo Garc燰
Vote (2)
Watch (5)

Dates

  • Created:
    Updated:
    Resolved: