Usage of plug-ins developed on Higher version to lower version
Accepted answer
You can try the same approach the other way around. However, your dependencies in the plug ins will have minimal version numbers, so you will get errors. You can try to remove the version numbers or replace the dependencies using the 2.x SDK. If you are using API that is not available in 2.x, you will have no choice but to replace the API by API available in 2.x.
Comments
Hello Ralph,
"C:\Workspace\Workspace.metadata.plugins\org.eclipse.pde.core\temp\org.eclipse.pde.container.feature\assemble.org.eclipse.pde.container.feature.p2.xml:39: The reference to entity "D_Hello_Plug-in" must end with the ';' delimiter.
project area is created on RTC 4.0 server
I just,
-
Connected with a 3.0.1 Eclipse workspace set up with the 3.0.1 SDK to a 4.0. Server
- Shared my fully compilable, error free Extensions from the 3.0.1 Extension workshop to a 3.0.1 Dev repo workspace
- Created a Steam ExtDev and flowed the changes there
- Connected with a 4.0 Eclipse workspace setup for the 4.0 SDK
-
Created a repo workspace 4.0 dev from the ExtDev Stream
- Loaded the workspace
No Compiler errors whatsoever. Not sure what trouble your P2 install does. I have a plain vanilla RTC client that I just unzipped for 4.x and 3.0.1. i have not testing deploying and no time to, but I would not expect issues. I would however set both workspaces to UTF8 as described in the Extension Workshop.
And I get a different error when building the update site.
Which is related to the fact that my feature contained a dependency to another feature that should not have been there in the first place. I removed that and now it builds just fine.
I think I forgot to mention I did NOT share the projects that are related to the 3.x or the 4.x SDK. I only shared the extensions that I had created.
The bove imples that the projects in Eclipse/RTC were created with RTC 3.x. the project area is 4.x.
The problems you see seem to be related with the Eclipse workspace. Not sure what the issue could be, since m approach worked for me.
And looking at the original question, you can not run an RTC 2.x against a 4.0 server. You can do what I did with 3.x and 4.x but not with 2.x since the server would complain. If you do want to bring your extensions over, you should export them and then import them into a workspace set up with 4.x SDK.
Hi Ralph,
What I tried to say is that I did not share the license files and other plug ins imported during setup of the Eclipse workspace for each version of the SDK. The setup process is different and different plug ins are imported. You need to make sure not to mix them up if using the same stream to share the projects you develop.
1 vote
Thanks Ralph...