[
https://issues.jboss.org/browse/JBIDE-26673?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-26673:
------------------------------------
I'm baffled. RSE is a "dead" project (insofar as there's one active
committer, just keeping the builds going -- me! -- with infrequent contributions from
Jeff) but instead of IBM *contributing* to it they've *_forked it internally and
updated it to 4.6_*?
How is that commitment to open source?
*
https://www.itprotoday.com/linux/ibm-open-source-success-requires-give-an...
*
https://www.crn.com/slide-shows/cloud/ibm-ceo-ginni-rometty-s-5-biggest-s...
Please ask your colleagues at IBM to contribute to the RSE project at Eclipse, instead of
internal forking. The rising tide won't lift all our boats if you're in your super
secret submarine. :(
As an aside, if you look at the history of the project from the late 3.x to the current
4.x, you'll see that most of the recent changes are just upversions and tweaks to keep
it compiling against the latest Eclipse. There have been no API breaks in moving from 3.x
to 4.x, just version number alignment between TM and RSE projects after they were merged
into one to break cyclic dependencies and make maintenance easier.
For example:
https://git.eclipse.org/c/tm/org.eclipse.tm.git/commit/?id=0650a822263d57...
https://git.eclipse.org/c/tm/org.eclipse.tm.git/diff/rse/plugins/org.ecli...
and
https://git.eclipse.org/c/tm/org.eclipse.tm.git/commit/?id=c49471f29d84b0...
https://git.eclipse.org/c/tm/org.eclipse.tm.git/diff/rse/features/org.ecl...
https://git.eclipse.org/c/tm/org.eclipse.tm.git/commit/?id=032879627037f0...
https://git.eclipse.org/c/tm/org.eclipse.tm.git/commit/?id=c78e6651377d16...
Dependency on org.eclipse.rse.ui 3.3 affects installation
---------------------------------------------------------
Key: JBIDE-26673
URL:
https://issues.jboss.org/browse/JBIDE-26673
Project: Tools (JBoss Tools)
Issue Type: Bug
Environment: This happens on eclipse Luna and Oxygen installing from the
marketplace or directly from eclipse when creating a new JBOSS server
Reporter: Manuel Parrao
Priority: Minor
Fix For: 4.12.x
I have a product that uses different plugins and some of them failed to be installed if
JBOSS tools are installed first since JBOSS tools has a dependency on org.eclipse.rse.ui
V3.3 and the other plugins I use work with org.eclipse.rse.ui V4.4 and org.eclipse.rse.ui
V4.6. On the other hand if I install first the other plugins and then try to install JBOSS
tools, JBOSS does not get installed due the same dependency issue.
Would it be possible to modify the manifest to accept org.eclipse.rse.ui 3.3 or later?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)