Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] [tm-dev] Any RSE dependencies in Neon?

Hello Kaloyan,


Why do you think moving RSE to an “orphan project” would simplify things ?

Why couldn’t interested parties maintain RSE in its current project ?





Martin Oberhuber, SMTS / Product Owner – Development Tools, Wind River

direct +43.662.457915.85  fax +43.662.457915.6


From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Kaloyan Raev
Sent: Saturday, December 12, 2015 9:15 AM
To: Cross project issues
Cc: TM project developer discussions
Subject: Re: [cross-project-issues-dev] [tm-dev] Any RSE dependencies in Neon?


The DLTK project contributes a DLTK RSE feature to the release train. My guess is that no one else on the release train depends on this DLTK RSE feature, so it would be easy to remove it if necessary.


From adopter's point of view, like JBoss Tools, Zend Studio also heavily relies on RSE.

The new o.e.remote really has some advantages like the Synchronized Project, but still misses some basic features of RSE:

  - Connecting to Windows systems (no cygwin please)

  - FTP connections

  - Remote Systems Explorer view, which allows browsing and editing files without creating a project on a remote system, but also on the local file system using the Local connection.


However, I suppose that Zend Studio, JBoss Tools and any other adopter can continue using RSE outside of the release train, while the project remains under the Eclipse Foundation.


BTW, something interesting I noticed is that IBM has already a fork of the RSE project. In the IBM Rational products the RSE plugins exist with the same org.eclipse.rse.* IDs, but with version 4.4.x. RSE under the Eclipse Foundation is still with version 3.7.2. This already causes a nasty fragmentation of RSE in the community. Any plugin that depends on the EF RSE most likely cannot be installed on IBM Rational due to dependency conflicts.


So, I have a suggestion. If the TM project has no interest in maintaining RSE in future, how about moving RSE to a new "orphan" project outside of the TM project, so those adopter who still rely on RSE can continue maintaining and improving it until they are ready to switch to the new alternative?





On Sat, Dec 12, 2015 at 9:17 AM, Max Rydahl Andersen <manderse@xxxxxxxxxx> wrote:

I know we are not on the release train but JBoss tools continues to use RSE.

Afaik there are still no replacement for the functionality it provides with respect to UI for connecting to ssh and ftp based systems.

If there are I would love to hear about them.

Thus my interest is still to keep it in.

If help is needed for including it let me know.


> On 11 Dec 2015, at 19:13, Greg Watson <g.watson@xxxxxxxxxxxx> wrote:
> Are there any projects that have a dependency on Remote System Explorer (RSE) in Neon? The TM project must decide if RSE will be included in the Neon release. Currently there is only interest in including TM Terminal.
> Thanks,
> Greg
> _______________________________________________
> tm-dev mailing list
> tm-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit

cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit


Back to the top