eclipse client compatibility.. seriously?
I am updating my dev/test system as I prepare for a new job.. install the latest client..
create repo connections.. what? 4.0.4 can't talk to 4.01, or 4.0.3 servers? you are kidding right? http://www-01.ibm.com/support/docview.wss?uid=swg21623665 |
Accepted answer
Sam,
No kidding. I currently have a 4.0.5 M2 Client for testing, and active 4.0.3 and 3.0.1 Clients for productive work in up to four different environments The reasoning makes sense, though: if you remain downwards compatible (a higher version server can talk to a lower version client) you can schedule the server upgrade and then - team by team - upgrade the clients. If it was only the other way around teams who could not upgrade yet would spoil it for everybody else desperately waiting for new server features. My guess is that ensuring both upward and downward compatibility would incur such an increase in costs that it would drive down the overall ability to bring new and desired feature into RTC. So your choices come down to: use a 4.0.1 client to access both 4.0.4 and 4.0.1 servers, or use two different Eclipse Clients (on the same computer) to have one of them be version level 4.0.4 Normally I add a disclaimer to please mark the answer as accepted if this answers your question, but in this case I fully understand if you abstain. Still, the only answer I have. Best, Arne Sreerupa Sen selected this answer as the correct answer
Comments
sam detweiler
commented Nov 24 '13, 11:08 a.m.
thanks.. the problem is I want the uplevel client function (delete attachments on 4.0.3) where it is supported. and you never know what the clients data formats might do to different workspaces.. there is no eclipse duplicate workspace.. altho I haven't tried copying the directory tree.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.