Tagged: Groovy-Eclipse Addin
- This topic has 3 replies, 3 voices, and was last updated 8 years, 3 months ago by Steven Hild.
-
AuthorPosts
-
Steven HildParticipantI am trying to upgrade to MyEclipse 2016 Stable 1.0 and we are using the Groovy-Eclipse addin. I am installing from: http://dist.springsource.org/snapshot/GRECLIPSE/e4.5/
I select to install:
Groovy-Eclipse
After expanding Extra Groovy compilers select Groovy Compiler 2.0 FeatureThe error I get is:
Cannot perform operation. Computing alternative solutions, may take a while: x/15
I then get an Install Remediation Page and it gives me 3 choices, one of which is disabled;
1. Keep my installation the same and modify the items being installed to be compatible
2. —- disabled —–
3. Show original error and build my own solutionSelect choice one and it says it will not install Groovy-Eclipse.
Select other choice I get the following detail:
Cannot complete the install because of a conflicting dependency.
Software being installed: Groovy-Eclipse Feature 2.9.2.xx-201607121857-e45 (org.codehaus.groovy.eclipse.feature.feature.group 2.9.2.xx-201607121857-e45)
Software currently installed: MyEclipse 2016 14.0.0.c0000002t201607141424 (package.2280-Grw-5198.windows.x86_64 14.0.0.c0000002t201607141424)
Only one of the following can be installed at once:
Java Development Tools Core 3.11.1.v20150902-1521 (org.eclipse.jdt.core 3.11.1.v20150902-1521)
Object Teams Development Tooling Core 3.11.1.v_OTDT_r241_201509081206 (org.eclipse.jdt.core 3.11.1.v_OTDT_r241_201509081206)
Java Development Tools Core 3.11.0.xx-201607121857-e45 (org.eclipse.jdt.core 3.11.0.xx-201607121857-e45)
Cannot satisfy dependency:
From: Groovy-Eclipse Compilerless Feature 2.9.2.xx-201607121857-e45 (org.codehaus.groovy.compilerless.feature.feature.group 2.9.2.xx-201607121857-e45)
To: org.codehaus.groovy.headless.feature.feature.group [2.9.2.xx-201607121857-e45]
Cannot satisfy dependency:
–Several more lines of Cannot satisfy dependency–
I contacted SpringSource and their person said:
The problem is a fixed version constraint inside of MyEclipse, as far as I can see.
Groovy-Eclipse installs a patched version of JDT. Therefore the patch replaces JDT (with a different version). This works just fine, for example, if you download and install Groovy-Eclipse on the Eclipse Mars 4.5.2 JEE package (for example).
In the case of MyEclipse it seems like the package definition of MyEclipse defines a dependency on a specific version of JDT (not JDT in general, which the Mars JEE package does). Therefore the install dialog complains about the conflict: it can’t satisfy the dependency from both (Groovy-Eclipse requires the patched version, MyEclipse requires a specific but different version).He said to ask you how they define the dependency on JDT and whether they can relax that declaration so that patched JDT versions can be installed.
The Groovy-Eclipse e4.4 installs fine with MyEclipse 2015 Stable 3.0
Thanks,
Steve
support-swapnaModeratorSteve,
Thank you for pointing to this issue. I could replicate the dependency issue at my end. I have filed a bug for the dev team and they are looking into it. We will keep you posted about the fix.
Apologies for inconvenience caused.
–Swapna
MyEclipse Support
Brian FernandesModeratorSteven,
We’ve fixed this in the 2016 CI 5 release earlier this week, and the fix will make it to the Stable 2.0 release as well – however, we will be releasing Stable 2.0 after a couple of months.
If you would like to try CI, you can install that alongside your existing Stable release.
Hope this helps.
Steven HildParticipantThanks Brian,
I’ll try the 2016 CI 5 release.
Steve
-
AuthorPosts