Use p2 Install Repository v4.0.x for existing Eclipse installation via links folder
.
`-- eclipse
`-- links
`-- RTC.link
!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.
2 answers
Comments
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.
RTC-Client-p2Repository-2.0.0.2iFix6
|-- features
|-- license
|-- plugins
|-- artifacts.xml
`-- content.xml
The only difference with the new one seems to be a binary folder:
RTC-Client-p2Repo-4.0.7
|-- binary
|-- features
|-- license
|-- plugins
|-- artifacts.xml
`-- content.xml
Simply compress these two files into the respective .jar files, and move the .xml files somewhere else, and the problem is gone.
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.
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).
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
$ cd RTC-Client-p2Repo-4.0.7
$ jar cf artifacts.jar artifacts.xml && rm artifacts.xml
$ jar cf content.jar content.xml && rm content.xml
!ENTRY org.eclipse.equinox.p2.engine 4 4 2015-04-16 15:37:48.975
!MESSAGE An error occurred while installing the items
!SUBENTRY 1 org.eclipse.equinox.p2.engine 4 0 2015-04-16 15:37:48.975
!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.hp.hpl.jena.rdf 2.7.2000.v20140124_0046, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction).
!SUBENTRY 1 org.eclipse.equinox.p2.touchpoint.eclipse 4 0 2015-04-16 15:37:48.975
!MESSAGE The artifact file for osgi.bundle,com.hp.hpl.jena.rdf,2.7.2000.v20140124_0046 was not found.
Comments
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?
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.
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.
We are updating the RTC version as well as the Eclipse IDE.
Comments
SEC Servizi
Apr 23 '15, 5:53 a.m.