[
https://issues.jboss.org/browse/JBIDE-22602?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-22602:
---------------------------------------
Wait a minute, how come the plugin is back? I checked JBIDE-21382 again and there you
said:
org.eclipse.core.runtime.compatibility 3.2.300.v20150423-0821 was removed from Neon as of
M3.
So we made sure we don't depend on it and eventually we removed it from our TP. How
come it's back?
TBH, I don't have a clue what's the correct state here. [~rob.stryker], do you
have an informed opinion on this? Is everything correct here?
Also, I could not find either of these plugins in my installation of the latest build of
devstudio:
{code}
$ find devstudio-11.1.0.AM1-847/studio/devstudio.app/ -name
'org.eclipse.core.runtime.compatibility*'
{code}
Same with 11 GA:
{code}
$ find devstudio-11.0.0.GA-748/studio/devstudio.app/ -name
'org.eclipse.core.runtime.compatibility*'
{code}
Check if org.eclipse.core.runtime.compatibility.auth is needed
--------------------------------------------------------------
Key: JBIDE-22602
URL:
https://issues.jboss.org/browse/JBIDE-22602
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: target-platform
Affects Versions: 4.4.0.Final
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.5.1.AM1
We removed org.eclipse.core.runtime.compatibility in JBIDE-21382 . But I noticed that we
still have org.eclipse.core.runtime.compatibility.auth in the TP (and devstudio
installation).
Do we need it? Shouldn't it be removed also?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)