2.5 compiler dependency breaking workaround for #317

[taikikim]

Our group has a project which is using Groovy 2.4. At an earlier point it was possible to keep only the 2.4 compiler installed, but it appears that as of GDT 3.0.0, the 2.5 compiler is now listed as a required dependency of GDT, and cannot be uninstalled separately from the main GDT feature.

This is causing problems with our workaround for #317, which to my understanding is triggered when more than one Groovy compiler version is installed. We're still able to work around the issue by manually deleting the plugin "org.codehaus.groovy_2.5.2" and feature "org.codehaus.groovy25.feature" from our Eclipse installation, but this needs to be repeated each time the plugin is updated and is obviously a non-ideal solution.

Assuming that there are still no plans to fix the issue described in #317, and that there is not a solution that I am missing to allow the 2.4 and 2.5 compilers to coexist: would it be possible to make the Compilerless feature available for independent installation, or otherwise provide some way to use a GDT installation without requiring the 2.5 compiler to be installed?

[eric-milles]

Groovy 2.5 was made the default in 3.1.0. It is an optional dependency; you should be able to go to Help > About Eclipse Platform > Installation Details > Installed Software, find it in the tree, and uninstall it. I think this will prevent it from coming back in an update because it is optional. (You may also use release 3.0.0, which maintains the 2.4 compiler as the default.)

It is not that I don't want this issue fixed; the compiler switching has been in place for a long long time and worked perfectly up until or through Eclipse Neon. Then something in the platform changed. I gave it my best effort to try and mitigate, but obviously the issue remains. You will need to take it to eclipse.org for a fix.

[mauromol]

@eric-milles Said that I never had any issue (with Oxygen or Photon either) to have multiple Groovy compiler versions installed (the most annoying thing I have to do is to switch the workspace-level compiler from one version to the other when it does not match the one I'm using in my projects), I was wondering whether you opened a bug to the Eclipse platform for this. I think you're the only one who can open a decent bug report, otherwise it's quite expected to see a "NOT_ECLIPSE" resolution from their side.

[eric-milles]

There seem to be a lot of similar bug reports that are not moving along: https://bugs.eclipse.org/bugs/buglist.cgi?quicksearch=%22invalid%20registry%20object%22