Shared resources directory and RTC 6.0.2 client for Eclipse 4.2.x
I develop a client extension for RTC. When I install RTC 6.0.2 client for Eclipse 4.2.x (from the repository) it installs most of the plugins to shared resources directory and not under the folder I set for the installation. This causes issues with an extension I have to org.eclipse.ui.startup. This extension is not activated when RTC starts. In plugin.xml there is message "No schema found for org.eclipse.ui.startup". After I reinstalled the message disappeared, but the issue remains, the extension is not activated on start-up.
Is there a way to install all RTC client under the path I set ?
By the way, the same issue is with RTC client 6.0.3 M4 for Eclipse 4.2.x. In 6.0.3 I also have issues with the views under "Work items" perspective. I get errors like "Could not create the view: com.ibm.magnolia.workItemExplorer".
Thanks,
Gidi
Accepted answer
Comments
Hello Donald,
Thanks for your reply on this issue. Yes, I installed through IBM installation manager. I tried installing the P2 for Eclipse 6.0.3 M4 on Eclipse 4.2.2 SDK 64 bit. There are two issues (I stopped there and turned to look at 6.0.2 instead):
1. The "Work Items" perspective is missing.
2. When I tried to set as my target platform the RTC SDK I got the following message:
"You have selected a target with a newer version than your current Eclipse installation. This can cause unexpected behavior in PDE. Please use a newer version of Eclipse."
I'll now try the same thing with RTC 6.0.2, will update soon about my findings.
Thanks again,
Gidi
I managed to run my plugin on RTC 6.0.2 client installed from P2 repository. I got a message "Warning: You are signing content that contains unsigned content..." which is weird, since 6.0.2 was already released.
One other answer
I had the "Could not create the view: com.ibm.magnolia.workItemExplorer" in version 7.0.2. The root cause was, that there were multiple org.apache.httpcomponents.hhtpclient, org.apache.httpcomponents.hhtpclient.win and org.apache.httpcomponents.hhtpcore jar files, each one in few, different versions. Removing one of the version of the (or changing the extension for them) resolved the issue.