Dependency conflict with IBM RTC 4.0.4

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Dependency conflict with IBM RTC 4.0.4

Yann Bourrigault
Hello everybody,

I've been trying for a few days now to install the Groovy-Eclipse 2.8.0 feature on an eclipse 4.2.2 where an IBM RTC client 4.0.4 is already installed, and I've been facing some dependency conflicts issues (see detailed log at the end of this mail). My understanding of this issue is that greclipse is providing a JDT core patch lying on the 3.8.3 version of org.eclipse.jdt.core (bundled in eclipse 4.2.2), whereas installing RTC upgrades the JDT core to version 3.8.4.

As I really need to have those both features running under the same eclipse, could you please provide me some help? I'm a Java developper, so recompiling the plugin does not frighten me, as long as you provide me some hints concerning the development environment setup.

Regards,
Yann.

Impossible de terminer l'installation à cause d'un conflit de dépendances
  Logiciel en cours d'installation : Groovy-Eclipse Feature 2.8.0.xx-20130703-1700-e42-RELEASE (org.codehaus.groovy.eclipse.feature.feature.group 2.8.0.xx-20130703-1700-e42-RELEASE)
  Logiciel actuellement installé : IBM Rational Team Concert Client 2013.11.2.135540 (IBM Rational Team Concert Client com.ibm.sdp.eclipse.ide 2013.11.2.135540)
  Un seul des éléments suivants peut être installé en même temps :
    Object Teams Development Tooling Core 3.8.1.v_OTDT_r210_201206090452 (org.eclipse.jdt.core 3.8.1.v_OTDT_r210_201206090452)
    Object Teams Development Tooling Core 3.8.3.v_OTDT_r212_201301271217 (org.eclipse.jdt.core 3.8.3.v_OTDT_r212_201301271217)
    Java Development Tools Core 3.8.1.v20120531-0637 (org.eclipse.jdt.core 3.8.1.v20120531-0637)
    Java Development Tools Core 3.8.3.xx-20140116-1600-e42-RELEASE (org.eclipse.jdt.core 3.8.3.xx-20140116-1600-e42-RELEASE)
    Object Teams Development Tooling Core 3.8.2.v_OTDT_r211_201209011847 (org.eclipse.jdt.core 3.8.2.v_OTDT_r211_201209011847)
    Java Development Tools Core 3.8.3.xx-20130703-1700-e42-RELEASE (org.eclipse.jdt.core 3.8.3.xx-20130703-1700-e42-RELEASE)
    Java Development Tools Core 3.8.4.v20130401-1038 (org.eclipse.jdt.core 3.8.4.v20130401-1038)
    Java Development Tools Core 3.8.2.v20120814-155456 (org.eclipse.jdt.core 3.8.2.v20120814-155456)
    Java Development Tools Core 3.8.3.v20130121-145325 (org.eclipse.jdt.core 3.8.3.v20130121-145325)
  Impossible de satisfaire la dépendance :
    De : IBM Rational Team Concert Client 2013.11.2.135540 (IBM Rational Team Concert Client com.ibm.sdp.eclipse.ide 2013.11.2.135540)
    Par rapport à : org.eclipse.jdt.R422patch.feature.group [1.0.4]
  Impossible de satisfaire la dépendance :
    De : IBM Rational Team Concert Client 2013.11.2.135540 (IBM Rational Team Concert Client com.ibm.sdp.eclipse.ide 2013.11.2.135540)
    Par rapport à : org.eclipse.jdt.feature.group [3.8.2.v20130116-090414-8-8nFu3FNOfwKLRuqgXKIy9z0I83,4.0.0)
  Impossible de satisfaire la dépendance :
    De : Groovy-Eclipse Feature 2.8.0.xx-20130703-1700-e42-RELEASE (org.codehaus.groovy.eclipse.feature.feature.group 2.8.0.xx-20130703-1700-e42-RELEASE)
    Par rapport à : org.codehaus.groovy.headless.feature.feature.group [2.8.0.xx-20130703-1700-e42-RELEASE]
  Impossible de satisfaire la dépendance :
    De : Groovy-Eclipse Headless Feature 2.8.0.xx-20130703-1700-e42-RELEASE (org.codehaus.groovy.headless.feature.feature.group 2.8.0.xx-20130703-1700-e42-RELEASE)
    Par rapport à : org.codehaus.groovy.jdt.patch.feature.group [2.8.0.xx-20130703-1700-e42-RELEASE]
  Impossible de satisfaire la dépendance :
    A partir du correctif : org.codehaus.groovy.jdt.patch.feature.group 2.8.0.xx-20130703-1700-e42-RELEASE Eclipse Java Development Tools 3.8.2.v20130116-090414-8-8nFu3FNOfwKLRuqgXKIy9z0I83 (org.eclipse.jdt.feature.group 3.8.2.v20130116-090414-8-8nFu3FNOfwKLRuqgXKIy9z0I83)
    Par rapport à : org.eclipse.jdt.core [3.8.3.xx-20130703-1700-e42-RELEASE]
  Impossible de satisfaire la dépendance :
    A partir du correctif : org.eclipse.jdt.R422patch.feature.group 1.0.4 Eclipse Java Development Tools 3.8.2.v20130116-090414-8-8nFu3FNOfwKLRuqgXKIy9z0I83 (org.eclipse.jdt.feature.group 3.8.2.v20130116-090414-8-8nFu3FNOfwKLRuqgXKIy9z0I83)
    Par rapport à : org.eclipse.jdt.core [3.8.4.v20130401-1038]
Reply | Threaded
Open this post in threaded view
|

Re: Dependency conflict with IBM RTC 4.0.4

Andy Clement
I suppose you could probably widen the version range for the groovy-eclipse patch such that it will install on top of 3.8.4 but it will then downgrade your compiler - if you were relying on some fixes in that more recent level of JDT then they won't be there.  To go down this road perhaps grab the downloadable update site, modify the version ranges in the relevant plugins and install from that customized update site.

Andy


On 19 February 2014 10:24, Yann Bourrigault <[hidden email]> wrote:
Hello everybody,

I've been trying for a few days now to install the Groovy-Eclipse 2.8.0 feature on an eclipse 4.2.2 where an IBM RTC client 4.0.4 is already installed, and I've been facing some dependency conflicts issues (see detailed log at the end of this mail). My understanding of this issue is that greclipse is providing a JDT core patch lying on the 3.8.3 version of org.eclipse.jdt.core (bundled in eclipse 4.2.2), whereas installing RTC upgrades the JDT core to version 3.8.4.

As I really need to have those both features running under the same eclipse, could you please provide me some help? I'm a Java developper, so recompiling the plugin does not frighten me, as long as you provide me some hints concerning the development environment setup.

Regards,
Yann.

Impossible de terminer l'installation à cause d'un conflit de dépendances
  Logiciel en cours d'installation : Groovy-Eclipse Feature 2.8.0.xx-20130703-1700-e42-RELEASE (org.codehaus.groovy.eclipse.feature.feature.group 2.8.0.xx-20130703-1700-e42-RELEASE)
  Logiciel actuellement installé : IBM Rational Team Concert Client 2013.11.2.135540 (IBM Rational Team Concert Client com.ibm.sdp.eclipse.ide 2013.11.2.135540)
  Un seul des éléments suivants peut être installé en même temps :
    Object Teams Development Tooling Core 3.8.1.v_OTDT_r210_201206090452 (org.eclipse.jdt.core 3.8.1.v_OTDT_r210_201206090452)
    Object Teams Development Tooling Core 3.8.3.v_OTDT_r212_201301271217 (org.eclipse.jdt.core 3.8.3.v_OTDT_r212_201301271217)
    Java Development Tools Core 3.8.1.v20120531-0637 (org.eclipse.jdt.core 3.8.1.v20120531-0637)
    Java Development Tools Core 3.8.3.xx-20140116-1600-e42-RELEASE (org.eclipse.jdt.core 3.8.3.xx-20140116-1600-e42-RELEASE)
    Object Teams Development Tooling Core 3.8.2.v_OTDT_r211_201209011847 (org.eclipse.jdt.core 3.8.2.v_OTDT_r211_201209011847)
    Java Development Tools Core 3.8.3.xx-20130703-1700-e42-RELEASE (org.eclipse.jdt.core 3.8.3.xx-20130703-1700-e42-RELEASE)
    Java Development Tools Core 3.8.4.v20130401-1038 (org.eclipse.jdt.core 3.8.4.v20130401-1038)
    Java Development Tools Core 3.8.2.v20120814-155456 (org.eclipse.jdt.core 3.8.2.v20120814-155456)
    Java Development Tools Core 3.8.3.v20130121-145325 (org.eclipse.jdt.core 3.8.3.v20130121-145325)
  Impossible de satisfaire la dépendance :
    De : IBM Rational Team Concert Client 2013.11.2.135540 (IBM Rational Team Concert Client com.ibm.sdp.eclipse.ide 2013.11.2.135540)
    Par rapport à : org.eclipse.jdt.R422patch.feature.group [1.0.4]
  Impossible de satisfaire la dépendance :
    De : IBM Rational Team Concert Client 2013.11.2.135540 (IBM Rational Team Concert Client com.ibm.sdp.eclipse.ide 2013.11.2.135540)
    Par rapport à : org.eclipse.jdt.feature.group [3.8.2.v20130116-090414-8-8nFu3FNOfwKLRuqgXKIy9z0I83,4.0.0)
  Impossible de satisfaire la dépendance :
    De : Groovy-Eclipse Feature 2.8.0.xx-20130703-1700-e42-RELEASE (org.codehaus.groovy.eclipse.feature.feature.group 2.8.0.xx-20130703-1700-e42-RELEASE)
    Par rapport à : org.codehaus.groovy.headless.feature.feature.group [2.8.0.xx-20130703-1700-e42-RELEASE]
  Impossible de satisfaire la dépendance :
    De : Groovy-Eclipse Headless Feature 2.8.0.xx-20130703-1700-e42-RELEASE (org.codehaus.groovy.headless.feature.feature.group 2.8.0.xx-20130703-1700-e42-RELEASE)
    Par rapport à : org.codehaus.groovy.jdt.patch.feature.group [2.8.0.xx-20130703-1700-e42-RELEASE]
  Impossible de satisfaire la dépendance :
    A partir du correctif : org.codehaus.groovy.jdt.patch.feature.group 2.8.0.xx-20130703-1700-e42-RELEASE Eclipse Java Development Tools 3.8.2.v20130116-090414-8-8nFu3FNOfwKLRuqgXKIy9z0I83 (org.eclipse.jdt.feature.group 3.8.2.v20130116-090414-8-8nFu3FNOfwKLRuqgXKIy9z0I83)
    Par rapport à : org.eclipse.jdt.core [3.8.3.xx-20130703-1700-e42-RELEASE]
  Impossible de satisfaire la dépendance :
    A partir du correctif : org.eclipse.jdt.R422patch.feature.group 1.0.4 Eclipse Java Development Tools 3.8.2.v20130116-090414-8-8nFu3FNOfwKLRuqgXKIy9z0I83 (org.eclipse.jdt.feature.group 3.8.2.v20130116-090414-8-8nFu3FNOfwKLRuqgXKIy9z0I83)
    Par rapport à : org.eclipse.jdt.core [3.8.4.v20130401-1038]

Reply | Threaded
Open this post in threaded view
|

Re: Dependency conflict with IBM RTC 4.0.4

Yann Bourrigault
Hello,

I've been trying widening the dependency of "org.codehaus.groovy.jdt.patch.feature.group" to my version of the JDT. The installation went smoothly, but then the opening of my groovy project failed with the following stack trace (various bundle activators also fail during startup for the same reason). Apparently the groovy plugin bundle could not be activated as the classes are not found. Do you think I should rebuild the plugin directly into my eclipse with the right version of the JDT?

Thanks,
Yann.

java.lang.NoClassDefFoundError: org/codehaus/jdt/groovy/integration/LanguageSupportFactory
    at org.codehaus.jdt.groovy.internal.compiler.ScriptFolderCompilationParticipant.sanityCheckBuilder(ScriptFolderCompilationParticipant.java:143)
    at org.codehaus.jdt.groovy.internal.compiler.ScriptFolderCompilationParticipant.buildStarting(ScriptFolderCompilationParticipant.java:104)
    at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.notifyParticipants(AbstractImageBuilder.java:566)
    at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.compile(AbstractImageBuilder.java:288)
    at org.eclipse.jdt.internal.core.builder.BatchImageBuilder.build(BatchImageBuilder.java:60)
    at org.eclipse.jdt.internal.core.builder.JavaBuilder.buildAll(JavaBuilder.java:254)
    at org.eclipse.jdt.internal.core.builder.JavaBuilder.build(JavaBuilder.java:173)
    at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:726)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239)
    at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295)
    at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351)
    at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374)
    at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
    at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Caused by: java.lang.ClassNotFoundException: org.codehaus.jdt.groovy.integration.LanguageSupportFactory
    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
    ... 19 more


Le Jeudi 20 février 2014 18h50, Andy Clement <[hidden email]> a écrit :
I suppose you could probably widen the version range for the groovy-eclipse patch such that it will install on top of 3.8.4 but it will then downgrade your compiler - if you were relying on some fixes in that more recent level of JDT then they won't be there.  To go down this road perhaps grab the downloadable update site, modify the version ranges in the relevant plugins and install from that customized update site.

Andy


On 19 February 2014 10:24, Yann Bourrigault <[hidden email]> wrote:
Hello everybody,

I've been trying for a few days now to install the Groovy-Eclipse 2.8.0 feature on an eclipse 4.2.2 where an IBM RTC client 4.0.4 is already installed, and I've been facing some dependency conflicts issues (see detailed log at the end of this mail). My understanding of this issue is that greclipse is providing a JDT core patch lying on the 3.8.3 version of org.eclipse.jdt.core (bundled in eclipse 4.2.2), whereas installing RTC upgrades the JDT core to version 3.8.4.

As I really need to have those both features running under the same eclipse, could you please provide me some help? I'm a Java developper, so recompiling the plugin does not frighten me, as long as you provide me some hints concerning the development environment setup.

Regards,
Yann.

Impossible de terminer l'installation à cause d'un conflit de dépendances
  Logiciel en cours d'installation : Groovy-Eclipse Feature 2.8.0.xx-20130703-1700-e42-RELEASE (org.codehaus.groovy.eclipse.feature.feature.group 2.8.0.xx-20130703-1700-e42-RELEASE)
  Logiciel actuellement installé : IBM Rational Team Concert Client 2013.11.2.135540 (IBM Rational Team Concert Client com.ibm.sdp.eclipse.ide 2013.11.2.135540)
  Un seul des éléments suivants peut être installé en même temps :
    Object Teams Development Tooling Core 3.8.1.v_OTDT_r210_201206090452 (org.eclipse.jdt.core 3.8.1.v_OTDT_r210_201206090452)
    Object Teams Development Tooling Core 3.8.3.v_OTDT_r212_201301271217 (org.eclipse.jdt.core 3.8.3.v_OTDT_r212_201301271217)
    Java Development Tools Core 3.8.1.v20120531-0637 (org.eclipse.jdt.core 3.8.1.v20120531-0637)
    Java Development Tools Core 3.8.3.xx-20140116-1600-e42-RELEASE (org.eclipse.jdt.core 3.8.3.xx-20140116-1600-e42-RELEASE)
    Object Teams Development Tooling Core 3.8.2.v_OTDT_r211_201209011847 (org.eclipse.jdt.core 3.8.2.v_OTDT_r211_201209011847)
    Java Development Tools Core 3.8.3.xx-20130703-1700-e42-RELEASE (org.eclipse.jdt.core 3.8.3.xx-20130703-1700-e42-RELEASE)
    Java Development Tools Core 3.8.4.v20130401-1038 (org.eclipse.jdt.core 3.8.4.v20130401-1038)
    Java Development Tools Core 3.8.2.v20120814-155456 (org.eclipse.jdt.core 3.8.2.v20120814-155456)
    Java Development Tools Core 3.8.3.v20130121-145325 (org.eclipse.jdt.core 3.8.3.v20130121-145325)
  Impossible de satisfaire la dépendance :
    De : IBM Rational Team Concert Client 2013.11.2.135540 (IBM Rational Team Concert Client com.ibm.sdp.eclipse.ide 2013.11.2.135540)
    Par rapport à : org.eclipse.jdt.R422patch.feature.group [1.0.4]
  Impossible de satisfaire la dépendance :
    De : IBM Rational Team Concert Client 2013.11.2.135540 (IBM Rational Team Concert Client com.ibm.sdp.eclipse.ide 2013.11.2.135540)
    Par rapport à : org.eclipse.jdt.feature.group [3.8.2.v20130116-090414-8-8nFu3FNOfwKLRuqgXKIy9z0I83,4.0.0)
  Impossible de satisfaire la dépendance :
    De : Groovy-Eclipse Feature 2.8.0.xx-20130703-1700-e42-RELEASE (org.codehaus.groovy.eclipse.feature.feature.group 2.8.0.xx-20130703-1700-e42-RELEASE)
    Par rapport à : org.codehaus.groovy.headless.feature.feature.group [2.8.0.xx-20130703-1700-e42-RELEASE]
  Impossible de satisfaire la dépendance :
    De : Groovy-Eclipse Headless Feature 2.8.0.xx-20130703-1700-e42-RELEASE (org.codehaus.groovy.headless.feature.feature.group 2.8.0.xx-20130703-1700-e42-RELEASE)
    Par rapport à : org.codehaus.groovy.jdt.patch.feature.group [2.8.0.xx-20130703-1700-e42-RELEASE]
  Impossible de satisfaire la dépendance :
    A partir du correctif : org.codehaus.groovy.jdt.patch.feature.group 2.8.0.xx-20130703-1700-e42-RELEASE Eclipse Java Development Tools 3.8.2.v20130116-090414-8-8nFu3FNOfwKLRuqgXKIy9z0I83 (org.eclipse.jdt.feature.group 3.8.2.v20130116-090414-8-8nFu3FNOfwKLRuqgXKIy9z0I83)
    Par rapport à : org.eclipse.jdt.core [3.8.3.xx-20130703-1700-e42-RELEASE]
  Impossible de satisfaire la dépendance :
    A partir du correctif : org.eclipse.jdt.R422patch.feature.group 1.0.4 Eclipse Java Development Tools 3.8.2.v20130116-090414-8-8nFu3FNOfwKLRuqgXKIy9z0I83 (org.eclipse.jdt.feature.group 3.8.2.v20130116-090414-8-8nFu3FNOfwKLRuqgXKIy9z0I83)
    Par rapport à : org.eclipse.jdt.core [3.8.4.v20130401-1038]



Reply | Threaded
Open this post in threaded view
|

Re: Dependency conflict with IBM RTC 4.0.4

Andy Clement
That exception suggests the patched jdt from groovy eclipse was not installed or at least is not being picked up. Perhaps in addition to widening the version to allow install you need to ensure the version of the groovy patch is later than the jdt version so it is also picked up in preference to it.

You could repatch your version of jdt yourself but that is a lot of messing about - i feel you should be able to get it to behave by tweaking the version numbers within plugins/features.  

Andy


On 23 February 2014 23:22, Yann Bourrigault <[hidden email]> wrote:
Hello,

I've been trying widening the dependency of "org.codehaus.groovy.jdt.patch.feature.group" to my version of the JDT. The installation went smoothly, but then the opening of my groovy project failed with the following stack trace (various bundle activators also fail during startup for the same reason). Apparently the groovy plugin bundle could not be activated as the classes are not found. Do you think I should rebuild the plugin directly into my eclipse with the right version of the JDT?

Thanks,
Yann.

java.lang.NoClassDefFoundError: org/codehaus/jdt/groovy/integration/LanguageSupportFactory
    at org.codehaus.jdt.groovy.internal.compiler.ScriptFolderCompilationParticipant.sanityCheckBuilder(ScriptFolderCompilationParticipant.java:143)
    at org.codehaus.jdt.groovy.internal.compiler.ScriptFolderCompilationParticipant.buildStarting(ScriptFolderCompilationParticipant.java:104)
    at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.notifyParticipants(AbstractImageBuilder.java:566)
    at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.compile(AbstractImageBuilder.java:288)
    at org.eclipse.jdt.internal.core.builder.BatchImageBuilder.build(BatchImageBuilder.java:60)
    at org.eclipse.jdt.internal.core.builder.JavaBuilder.buildAll(JavaBuilder.java:254)
    at org.eclipse.jdt.internal.core.builder.JavaBuilder.build(JavaBuilder.java:173)
    at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:726)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239)
    at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295)
    at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351)
    at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374)
    at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
    at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Caused by: java.lang.ClassNotFoundException: org.codehaus.jdt.groovy.integration.LanguageSupportFactory
    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
    ... 19 more


Le Jeudi 20 février 2014 18h50, Andy Clement <[hidden email]> a écrit :
I suppose you could probably widen the version range for the groovy-eclipse patch such that it will install on top of 3.8.4 but it will then downgrade your compiler - if you were relying on some fixes in that more recent level of JDT then they won't be there.  To go down this road perhaps grab the downloadable update site, modify the version ranges in the relevant plugins and install from that customized update site.

Andy


On 19 February 2014 10:24, Yann Bourrigault <[hidden email]> wrote:
Hello everybody,

I've been trying for a few days now to install the Groovy-Eclipse 2.8.0 feature on an eclipse 4.2.2 where an IBM RTC client 4.0.4 is already installed, and I've been facing some dependency conflicts issues (see detailed log at the end of this mail). My understanding of this issue is that greclipse is providing a JDT core patch lying on the 3.8.3 version of org.eclipse.jdt.core (bundled in eclipse 4.2.2), whereas installing RTC upgrades the JDT core to version 3.8.4.

As I really need to have those both features running under the same eclipse, could you please provide me some help? I'm a Java developper, so recompiling the plugin does not frighten me, as long as you provide me some hints concerning the development environment setup.

Regards,
Yann.

Impossible de terminer l'installation à cause d'un conflit de dépendances
  Logiciel en cours d'installation : Groovy-Eclipse Feature 2.8.0.xx-20130703-1700-e42-RELEASE (org.codehaus.groovy.eclipse.feature.feature.group 2.8.0.xx-20130703-1700-e42-RELEASE)
  Logiciel actuellement installé : IBM Rational Team Concert Client 2013.11.2.135540 (IBM Rational Team Concert Client com.ibm.sdp.eclipse.ide 2013.11.2.135540)
  Un seul des éléments suivants peut être installé en même temps :
    Object Teams Development Tooling Core 3.8.1.v_OTDT_r210_201206090452 (org.eclipse.jdt.core 3.8.1.v_OTDT_r210_201206090452)
    Object Teams Development Tooling Core 3.8.3.v_OTDT_r212_201301271217 (org.eclipse.jdt.core 3.8.3.v_OTDT_r212_201301271217)
    Java Development Tools Core 3.8.1.v20120531-0637 (org.eclipse.jdt.core 3.8.1.v20120531-0637)
    Java Development Tools Core 3.8.3.xx-20140116-1600-e42-RELEASE (org.eclipse.jdt.core 3.8.3.xx-20140116-1600-e42-RELEASE)
    Object Teams Development Tooling Core 3.8.2.v_OTDT_r211_201209011847 (org.eclipse.jdt.core 3.8.2.v_OTDT_r211_201209011847)
    Java Development Tools Core 3.8.3.xx-20130703-1700-e42-RELEASE (org.eclipse.jdt.core 3.8.3.xx-20130703-1700-e42-RELEASE)
    Java Development Tools Core 3.8.4.v20130401-1038 (org.eclipse.jdt.core 3.8.4.v20130401-1038)
    Java Development Tools Core 3.8.2.v20120814-155456 (org.eclipse.jdt.core 3.8.2.v20120814-155456)
    Java Development Tools Core 3.8.3.v20130121-145325 (org.eclipse.jdt.core 3.8.3.v20130121-145325)
  Impossible de satisfaire la dépendance :
    De : IBM Rational Team Concert Client 2013.11.2.135540 (IBM Rational Team Concert Client com.ibm.sdp.eclipse.ide 2013.11.2.135540)
    Par rapport à : org.eclipse.jdt.R422patch.feature.group [1.0.4]
  Impossible de satisfaire la dépendance :
    De : IBM Rational Team Concert Client 2013.11.2.135540 (IBM Rational Team Concert Client com.ibm.sdp.eclipse.ide 2013.11.2.135540)
    Par rapport à : org.eclipse.jdt.feature.group [3.8.2.v20130116-090414-8-8nFu3FNOfwKLRuqgXKIy9z0I83,4.0.0)
  Impossible de satisfaire la dépendance :
    De : Groovy-Eclipse Feature 2.8.0.xx-20130703-1700-e42-RELEASE (org.codehaus.groovy.eclipse.feature.feature.group 2.8.0.xx-20130703-1700-e42-RELEASE)
    Par rapport à : org.codehaus.groovy.headless.feature.feature.group [2.8.0.xx-20130703-1700-e42-RELEASE]
  Impossible de satisfaire la dépendance :
    De : Groovy-Eclipse Headless Feature 2.8.0.xx-20130703-1700-e42-RELEASE (org.codehaus.groovy.headless.feature.feature.group 2.8.0.xx-20130703-1700-e42-RELEASE)
    Par rapport à : org.codehaus.groovy.jdt.patch.feature.group [2.8.0.xx-20130703-1700-e42-RELEASE]
  Impossible de satisfaire la dépendance :
    A partir du correctif : org.codehaus.groovy.jdt.patch.feature.group 2.8.0.xx-20130703-1700-e42-RELEASE Eclipse Java Development Tools 3.8.2.v20130116-090414-8-8nFu3FNOfwKLRuqgXKIy9z0I83 (org.eclipse.jdt.feature.group 3.8.2.v20130116-090414-8-8nFu3FNOfwKLRuqgXKIy9z0I83)
    Par rapport à : org.eclipse.jdt.core [3.8.3.xx-20130703-1700-e42-RELEASE]
  Impossible de satisfaire la dépendance :
    A partir du correctif : org.eclipse.jdt.R422patch.feature.group 1.0.4 Eclipse Java Development Tools 3.8.2.v20130116-090414-8-8nFu3FNOfwKLRuqgXKIy9z0I83 (org.eclipse.jdt.feature.group 3.8.2.v20130116-090414-8-8nFu3FNOfwKLRuqgXKIy9z0I83)
    Par rapport à : org.eclipse.jdt.core [3.8.4.v20130401-1038]




Reply | Threaded
Open this post in threaded view
|

Re: Dependency conflict with IBM RTC 4.0.4

Yann Bourrigault
Hello,

I finally managed to make it work. I followed the following steps:
- Change the version of the org.eclipse.jdt.core project to match the version provided by RTC (3.8.4.v20130401-1038) & remove the signatures from the jar
- Change the dependency version in the org.codehaus.groovy.jdt.patch.feature.group with the new version of the org.eclipse.jdt.core & remove signatures from the jar
- Change the md5 hashes in artifacts.xml
- Change the org.eclipse.jdt.core dependency version in content.xml

I installed this plugin on a new eclipse 4.2.2, and I was then able to install the RTC plugin over it (as the installed jdt.core patch made the RTC one useless).

During one of my desperate tries I migrated the groovy patch over the last org.eclipse.jdt.core 3.8.4. It turned out that the problem I had at this time was not related to this, so I finally used the version you provide, but if you're interested I might provide you the source code of this update.

Thanks for the support,

Yann.



Le Lundi 24 février 2014 17h22, Andy Clement <[hidden email]> a écrit :
That exception suggests the patched jdt from groovy eclipse was not installed or at least is not being picked up. Perhaps in addition to widening the version to allow install you need to ensure the version of the groovy patch is later than the jdt version so it is also picked up in preference to it.

You could repatch your version of jdt yourself but that is a lot of messing about - i feel you should be able to get it to behave by tweaking the version numbers within plugins/features.  

Andy


On 23 February 2014 23:22, Yann Bourrigault <[hidden email]> wrote:
Hello,

I've been trying widening the dependency of "org.codehaus.groovy.jdt.patch.feature.group" to my version of the JDT. The installation went smoothly, but then the opening of my groovy project failed with the following stack trace (various bundle activators also fail during startup for the same reason). Apparently the groovy plugin bundle could not be activated as the classes are not found. Do you think I should rebuild the plugin directly into my eclipse with the right version of the JDT?

Thanks,
Yann.

java.lang.NoClassDefFoundError: org/codehaus/jdt/groovy/integration/LanguageSupportFactory
    at org.codehaus.jdt.groovy.internal.compiler.ScriptFolderCompilationParticipant.sanityCheckBuilder(ScriptFolderCompilationParticipant.java:143)
    at org.codehaus.jdt.groovy.internal.compiler.ScriptFolderCompilationParticipant.buildStarting(ScriptFolderCompilationParticipant.java:104)
    at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.notifyParticipants(AbstractImageBuilder.java:566)
    at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.compile(AbstractImageBuilder.java:288)
    at org.eclipse.jdt.internal.core.builder.BatchImageBuilder.build(BatchImageBuilder.java:60)
    at org.eclipse.jdt.internal.core.builder.JavaBuilder.buildAll(JavaBuilder.java:254)
    at org.eclipse.jdt.internal.core.builder.JavaBuilder.build(JavaBuilder.java:173)
    at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:726)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239)
    at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295)
    at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351)
    at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374)
    at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
    at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Caused by: java.lang.ClassNotFoundException: org.codehaus.jdt.groovy.integration.LanguageSupportFactory
    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
    at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
    ... 19 more


Le Jeudi 20 février 2014 18h50, Andy Clement <[hidden email]> a écrit :
I suppose you could probably widen the version range for the groovy-eclipse patch such that it will install on top of 3.8.4 but it will then downgrade your compiler - if you were relying on some fixes in that more recent level of JDT then they won't be there.  To go down this road perhaps grab the downloadable update site, modify the version ranges in the relevant plugins and install from that customized update site.

Andy


On 19 February 2014 10:24, Yann Bourrigault <[hidden email]> wrote:
Hello everybody,

I've been trying for a few days now to install the Groovy-Eclipse 2.8.0 feature on an eclipse 4.2.2 where an IBM RTC client 4.0.4 is already installed, and I've been facing some dependency conflicts issues (see detailed log at the end of this mail). My understanding of this issue is that greclipse is providing a JDT core patch lying on the 3.8.3 version of org.eclipse.jdt.core (bundled in eclipse 4.2.2), whereas installing RTC upgrades the JDT core to version 3.8.4.

As I really need to have those both features running under the same eclipse, could you please provide me some help? I'm a Java developper, so recompiling the plugin does not frighten me, as long as you provide me some hints concerning the development environment setup.

Regards,
Yann.

Impossible de terminer l'installation à cause d'un conflit de dépendances
  Logiciel en cours d'installation : Groovy-Eclipse Feature 2.8.0.xx-20130703-1700-e42-RELEASE (org.codehaus.groovy.eclipse.feature.feature.group 2.8.0.xx-20130703-1700-e42-RELEASE)
  Logiciel actuellement installé : IBM Rational Team Concert Client 2013.11.2.135540 (IBM Rational Team Concert Client com.ibm.sdp.eclipse.ide 2013.11.2.135540)
  Un seul des éléments suivants peut être installé en même temps :
    Object Teams Development Tooling Core 3.8.1.v_OTDT_r210_201206090452 (org.eclipse.jdt.core 3.8.1.v_OTDT_r210_201206090452)
    Object Teams Development Tooling Core 3.8.3.v_OTDT_r212_201301271217 (org.eclipse.jdt.core 3.8.3.v_OTDT_r212_201301271217)
    Java Development Tools Core 3.8.1.v20120531-0637 (org.eclipse.jdt.core 3.8.1.v20120531-0637)
    Java Development Tools Core 3.8.3.xx-20140116-1600-e42-RELEASE (org.eclipse.jdt.core 3.8.3.xx-20140116-1600-e42-RELEASE)
    Object Teams Development Tooling Core 3.8.2.v_OTDT_r211_201209011847 (org.eclipse.jdt.core 3.8.2.v_OTDT_r211_201209011847)
    Java Development Tools Core 3.8.3.xx-20130703-1700-e42-RELEASE (org.eclipse.jdt.core 3.8.3.xx-20130703-1700-e42-RELEASE)
    Java Development Tools Core 3.8.4.v20130401-1038 (org.eclipse.jdt.core 3.8.4.v20130401-1038)
    Java Development Tools Core 3.8.2.v20120814-155456 (org.eclipse.jdt.core 3.8.2.v20120814-155456)
    Java Development Tools Core 3.8.3.v20130121-145325 (org.eclipse.jdt.core 3.8.3.v20130121-145325)
  Impossible de satisfaire la dépendance :
    De : IBM Rational Team Concert Client 2013.11.2.135540 (IBM Rational Team Concert Client com.ibm.sdp.eclipse.ide 2013.11.2.135540)
    Par rapport à : org.eclipse.jdt.R422patch.feature.group [1.0.4]
  Impossible de satisfaire la dépendance :
    De : IBM Rational Team Concert Client 2013.11.2.135540 (IBM Rational Team Concert Client com.ibm.sdp.eclipse.ide 2013.11.2.135540)
    Par rapport à : org.eclipse.jdt.feature.group [3.8.2.v20130116-090414-8-8nFu3FNOfwKLRuqgXKIy9z0I83,4.0.0)
  Impossible de satisfaire la dépendance :
    De : Groovy-Eclipse Feature 2.8.0.xx-20130703-1700-e42-RELEASE (org.codehaus.groovy.eclipse.feature.feature.group 2.8.0.xx-20130703-1700-e42-RELEASE)
    Par rapport à : org.codehaus.groovy.headless.feature.feature.group [2.8.0.xx-20130703-1700-e42-RELEASE]
  Impossible de satisfaire la dépendance :
    De : Groovy-Eclipse Headless Feature 2.8.0.xx-20130703-1700-e42-RELEASE (org.codehaus.groovy.headless.feature.feature.group 2.8.0.xx-20130703-1700-e42-RELEASE)
    Par rapport à : org.codehaus.groovy.jdt.patch.feature.group [2.8.0.xx-20130703-1700-e42-RELEASE]
  Impossible de satisfaire la dépendance :
    A partir du correctif : org.codehaus.groovy.jdt.patch.feature.group 2.8.0.xx-20130703-1700-e42-RELEASE Eclipse Java Development Tools 3.8.2.v20130116-090414-8-8nFu3FNOfwKLRuqgXKIy9z0I83 (org.eclipse.jdt.feature.group 3.8.2.v20130116-090414-8-8nFu3FNOfwKLRuqgXKIy9z0I83)
    Par rapport à : org.eclipse.jdt.core [3.8.3.xx-20130703-1700-e42-RELEASE]
  Impossible de satisfaire la dépendance :
    A partir du correctif : org.eclipse.jdt.R422patch.feature.group 1.0.4 Eclipse Java Development Tools 3.8.2.v20130116-090414-8-8nFu3FNOfwKLRuqgXKIy9z0I83 (org.eclipse.jdt.feature.group 3.8.2.v20130116-090414-8-8nFu3FNOfwKLRuqgXKIy9z0I83)
    Par rapport à : org.eclipse.jdt.core [3.8.4.v20130401-1038]