Use p2 Install Repository v4.0.x for existing Eclipse installation via links folder
We used to install the Rational Team Concert client into a supported version of Eclipse via link folder and pointing to the p2 Install Repository files.
We are still on RTC v2.0.0.2 and our current configuration is (kinda):
.
`-- eclipse
`-- links
`-- RTC.link
We are preparing to migrate to RTC v4.0.7 and if we set the 'RTC.link' file to use the content of RTC-Client-p2Repo-4.0.7.zip, we are not able to use this approach anymore:
!ENTRY org.eclipse.equinox.p2.engine 4 4 2015-04-15 17:01:16.064 !MESSAGE An error occurred while installing the items !SUBENTRY 1 org.eclipse.equinox.p2.engine 4 0 2015-04-15 17:01:16.064 !MESSAGE session context was:(profile=com.genuitec.delivery.package.profile.1912-lxl-1236, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null --> [R]com.ibm.team.concert.uuid.root.feature_root 4.3.1.RTC-I20140626-1252, action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.UnzipAction). !SUBENTRY 1 org.eclipse.equinox.p2.touchpoint.natives 4 0 2015-04-15 17:01:16.064 !MESSAGE The artifact for binary,com.ibm.team.concert.uuid.root.feature_root,4.3.1.RTC-I20140626-1252 is not available.
Any advice?
Thanks in advance.
|
2 answers
This is a curious case - I can see the same issue with the RTC 4.0.6 p2 package.
In the root folder of the package, there should be two files artifacts.jar and contents.jar, but artifacts.xml and contents.xml (unpacked) are there instead. This simple fact seems to confuse the Eclipse p2 installer. Simply compress these two files into the respective .jar files, and move the .xml files somewhere else, and the problem is gone.
Comments
We notice these two files are unpacked even in the older p2 repository:
RTC-Client-p2Repository-2.0.0.2iFix6 The only difference with the new one seems to be a binary folder: RTC-Client-p2Repo-4.0.7
Anyway, we will give your suggestion a try:
Thanks for the advice, Donald.
Donald Nong
commented Apr 21 '15, 6:38 a.m.
I remember seeing a notification saying that it worked but later you edited the post and said it did not work. So what happened? I tested with RTC 4.0.7 p2 package with a RTC 3.0.1.1 client (the oldest I could find) and managed to upgrade it without major issues - just had to restart the RTC Eclipse client twice to finish the installation.
SEC Servizi
commented Apr 23 '15, 4:19 a.m.
I remember seeing a notification saying that it worked but later you edited the post and said it did not work. So what happened? Sadly, it was a false positive result (due to a mistaken configuration).
We are not going to update an existing RTC client. Instead, we would install/use the RTC client plug-ins in all our Eclipse based IDEs.
|
We tried Donald's trick:
$ cd RTC-Client-p2Repo-4.0.7
but it did not work... The error message now is:
!ENTRY org.eclipse.equinox.p2.engine 4 4 2015-04-16 15:37:48.975 Comments
Donald Nong
commented Apr 23 '15, 6:15 a.m.
You will need to be very specific about the configuration that is having the issue. I just tried with plain Eclipse 3.5, and only part of the RTC components got installed and I had a perspective called "Jazz Administration". Strange, right?
SEC Servizi
commented Apr 23 '15, 10:14 a.m.
I just tried with plain Eclipse 3.5, and only part of the RTC components got installed On IBM RSA v8.5 we could observe the RTC client plug-ins appear to be present, but in fact the log lists: !ENTRY org.eclipse.equinox.p2.engine 4 4 2015-04-23 11:25:23.122 !MESSAGE An error occurred while installing the items !SUBENTRY 1 org.eclipse.equinox.p2.engine 4 0 2015-04-23 11:25:23.122 !MESSAGE session context was:(profile=bootProfile, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null --> [R]com.ibm.team.concert.uuid.root.feature_root 4.3.1.RTC-I20140626-1252, action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.UnzipAction). !SUBENTRY 1 org.eclipse.equinox.p2.touchpoint.natives 4 0 2015-04-23 11:25:23.122 !MESSAGE The artifact for binary,com.ibm.team.concert.uuid.root.feature_root,4.3.1.RTC-I20140626-1252 is not available.
Donald Nong
commented Apr 24 '15, 3:35 a.m.
I forgot to mention, there is no common Eclipse version that is officially supported by both RTC 2.0.0.x and RTC 4.0.7. So your current Eclipse version does make a (huge) difference. My tests showed that Eclipse 3.5.2 (RTC 3.0.1) still works, but Eclipse 3.5 fails.
SEC Servizi
commented Apr 24 '15, 9:13 a.m.
We are updating the RTC version as well as the Eclipse IDE. |
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.
Comments