| In that case I think we need to rethink how PTP and RDT are packaged. For users installing PTP + RDT, the Remote Tools indexing support is not optional so must be included as part of the install, otherwise RDT is broken. However, RSE *is* optional for PTP, so this feature can't be included in the PTP End User Runtime as RDT (and consequently the Remote Tools indexing feature) has an RSE dependency. Just naming it differently doesn't address the core issue that the feature is actually mandatory for PTP + RDT, and as user experience is our first priority, having RDT break because the user overlooks a feature is not an option in my view.
Maybe the way to do this would be to have three features: PTP only, RDT only, and PTP + RDT? Unfortunately we no longer have time to make changes as SR1 is now frozen. This will have to be targeted for SR2 or PTP 5.0.
Greg On Sep 17, 2010, at 8:43 AM, Chris Recoskie wrote: I would rather not, as we reship RDT in our IBM products and do not wish to ship the Remote Tools indexing provider with it. We modify the server, so having users try to connect to the one bundled with the Remote Tools provider would make for a very broken experience in our case, as it would be lacking all of our customizations.
I would suggest finding a way of making the PTP RDT Remote Tools Support easier to find, or make it so that it's named in such a way that users are more likely to know they need it. If you were to call it "PTP RDT SSH-based server support" or somesuch, that might help.
===========================
Chris Recoskie
Team Lead, IBM CDT and RDT
IBM Toronto
<graycol.gif>Beth Tibbitts ---09/16/2010 09:15:53 PM---When you install PTP end-user runtime, and RDT, why should you have to install another obscure
<ecblank.gif>
From: | <ecblank.gif>
Beth Tibbitts <tibbitts@xxxxxxxxxx> |
<ecblank.gif>
To: | <ecblank.gif>
ptp-dev@xxxxxxxxxxx |
<ecblank.gif>
Date: | <ecblank.gif>
09/16/2010 09:15 PM |
<ecblank.gif>
Subject: | <ecblank.gif>
[ptp-dev] RDT/PTP needs to include PTP RDT Remote Tools Support feature |
<ecblank.gif>
Sent by: | <ecblank.gif>
ptp-dev-bounces@xxxxxxxxxxx |
When you install PTP end-user runtime, and RDT, why should you have to install another obscure
component in order to get Remote Tools to work?
It's too confusing to users.
But yet if you don't install the PTP RDT Remote Tools Support, the RDT remote indexing
server doesn't get started, and nothing tells you that anything is missing.
I have been testing installs all week getting ready for helios sr1 and for our PTP tutorial at SC10,
and it just doesn't make sense that the user should have to know that.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=325536
Product/Component: PTP / RDT
Can we please make it a default inclusion in RDT?
It doesn't look like it adds any additional dependencies to RDT.
...Beth
Beth Tibbitts
Eclipse Parallel Tools Platform http://eclipse.org/ptp
IBM STG Communications Protocols and Tools
Mailing Address: IBM Corp., Coldstream Research Campus, 745 West New Circle Road, Lexington, KY 40511_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
|
