It's even simpler than that. The plugin only has the same dependencies as the rest of RDT so it doesn't change the dependencies at all. If you do encounter any problems, let me know and we can repackage.On Sep 17, 2010, at 10:30 AM, Chris Recoskie wrote: If the dependencies of the new plugin are optional then I don't see a problem. The way you had originally described it though, it sounded like the dependencies of the plugin had been added to the dependencies of the feature, and that would have caused the breakage I described.
===========================
Chris Recoskie
Team Lead, IBM CDT and RDT
IBM Toronto
<graycol.gif>Greg Watson ---09/17/2010 10:22:29 AM---I'm sorry, but we only discovered what was a significant packaging error late last night and this wa
<ecblank.gif>
From: | <ecblank.gif>
Greg Watson <g.watson@xxxxxxxxxxxx> |
<ecblank.gif>
To: | <ecblank.gif>
Parallel Tools Platform general developers <ptp-dev@xxxxxxxxxxx> |
<ecblank.gif>
Date: | <ecblank.gif>
09/17/2010 10:22 AM |
<ecblank.gif>
Subject: | <ecblank.gif>
Re: [ptp-dev] RDT/PTP needs to include PTP RDT Remote Tools Support feature |
<ecblank.gif>
Sent by: | <ecblank.gif>
ptp-dev-bounces@xxxxxxxxxxx |
I'm sorry, but we only discovered what was a significant packaging error late last night and this was the last opportunity to get it into SR1. I don't believe this will affect your product packaging at all, as there are no dependency changes, nor will there be any translation issues, as the code will never be activated in your product. There were no changes to core RDT code, as this is already included in the new project wizard, so there is minimal risk associated with it.
If you do discovery any problems, which I think is highly unlikely, we can repackage for 4.0.4 next week. However, I'm confident that you will not see any differences.
Greg
On Sep 17, 2010, at 9:18 AM, Chris Recoskie wrote:
Well I'm very unhappy that this was done at the last minute because it really screws our product. It means that our product now can't install the RDT feature without Remote Tools. We now have to go and overhaul our entire build, packaging, and install process when our product is in the release candidate cycle. That is a very risky thing to do at this point. We are releasing in two weeks.
This also screws our translation efforts as now there would be all kinds of new strings showing up that are not translated.
I veto this change. We need to undo it.
Since SR1 is apparently frozen, I guess this means we need a 4.0.4 right away to fix this.
===========================
Chris Recoskie
Team Lead, IBM CDT and RDT
IBM Toronto
<graycol.gif>Greg Watson ---09/17/2010 09:09:26 AM---In that case I think we need to rethink how PTP and RDT are packaged. For users installing PTP + RDT
<ecblank.gif>
From: | <ecblank.gif>
Greg Watson <g.watson@xxxxxxxxxxxx> |
<ecblank.gif>
To: | <ecblank.gif>
Parallel Tools Platform general developers <ptp-dev@xxxxxxxxxxx> |
<ecblank.gif>
Date: | <ecblank.gif>
09/17/2010 09:09 AM |
<ecblank.gif>
Subject: | <ecblank.gif>
Re: [ptp-dev] RDT/PTP needs to include PTP RDT Remote Tools Support feature |
<ecblank.gif>
Sent by: | <ecblank.gif>
ptp-dev-bounces@xxxxxxxxxxx |
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
_______________________________________________
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
_______________________________________________
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
|
