Ashish Chandra created JBDS-2628:
------------------------------------
Summary: Cannot complete the install because of a conflicting dependency.
Key: JBDS-2628
URL:
https://issues.jboss.org/browse/JBDS-2628
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: RHEL 6.4, Drools 6.0.0.Beta2
Reporter: Ashish Chandra
Cannot complete the install because of a conflicting dependency.
Software being installed: JBoss Runtime Drools Detector 6.0.0.Beta2
(org.jboss.tools.runtime.drools.detector.feature.feature.group 6.0.0.Beta2)
Software currently installed: Eclipse Platform 3.6.0.M20100909-0800
(org.eclipse.platform.ide 3.6.0.M20100909-0800)
Only one of the following can be installed at once:
Debug Core 3.7.100.v20120521-2012 (org.eclipse.debug.core 3.7.100.v20120521-2012)
Debug Core 3.6.0.v20100519 (org.eclipse.debug.core 3.6.0.v20100519)
Cannot satisfy dependency:
From: Eclipse Platform 3.6.1.r361_v20100909-9pF78H4oFrRqnz-iz-wQGbTOTP5K6uL437qW
(org.eclipse.platform.feature.group
3.6.1.r361_v20100909-9pF78H4oFrRqnz-iz-wQGbTOTP5K6uL437qW)
To: org.eclipse.debug.core [3.6.0.v20100519]
Cannot satisfy dependency:
From: Eclipse Platform 3.6.0.M20100909-0800 (org.eclipse.platform.ide
3.6.0.M20100909-0800)
To: org.eclipse.platform.feature.group
[3.6.1.r361_v20100909-9pF78H4oFrRqnz-iz-wQGbTOTP5K6uL437qW]
Cannot satisfy dependency:
From: JBoss Tools Common Core 3.4.0.Final-v20130327-0606-B69
(org.jboss.tools.common.core.feature.feature.group 3.4.0.Final-v20130327-0606-B69)
To: org.jboss.tools.common.model [3.4.0.Final-v20130327-0606-B69]
Cannot satisfy dependency:
From: JBoss Tools Model 3.4.0.Final-v20130327-0606-B69 (org.jboss.tools.common.model
3.4.0.Final-v20130327-0606-B69)
To: bundle org.eclipse.debug.core 3.7.0
Cannot satisfy dependency:
From: JBoss Runtime Drools Detector 6.0.0.Beta2
(org.jboss.tools.runtime.drools.detector.feature.feature.group 6.0.0.Beta2)
To: org.jboss.tools.common.core.feature.feature.group 0.0.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira