Targlets and p2 profiles [message #1797468] |
Wed, 31 October 2018 06:17  |
Eclipse User |
|
|
|
Hi,
I am currently trying to use targlets to set the target platform for our development and I am facing problems with the following scenario.
Scenario
We are are developing plugins for an RCP coming from another vendor. This RCP is patched several times a year but the problem is that they are not upding the version numbers correctly so that p2 is recoginizing the newer plugins and thinks the existing ones does not need to be updated.
In the past we did not used bundle pools an then I only needed to delete the folder:
.metadata\.plugins\org.eclipse.pde.core
The problem with that solution is that every workspace has a complete target platform bundle pool. Which can be several GB of plug-ins. With targlets I want to be able share those plug-ins between workspaces.
What I did so far:
- Creating a targlet pointing to the p2-repository that contains the whole RCP
- Updating the OOMPH setup in the targlet to the new p2 repository containing the new plugins
- Making an update via oomph but the targlet resolvement is not picking the new ones up because the version pf the plugins have not been changed.
Questions:
1.. Is it possible to reset or remove a profile that contains athe bundles of a targlet so that the oomph update reusing the target to pick up the newer versions?
2. Can I use different bundlepools for the eclipse installation and the targlets so that I only need to delete the targlet bundlepool and use the oomph updater to recreate that bundle pool based on the new plugins?
3. Are there other ways of forcing a complete override or update?
4. I also have seen that after the update of the targlets new versions are only picked up after triggering a reload of the target platform. Can this be triggered by the oomph updater so that this manual step has not to be done anymore?
Regards
Lasse
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.07677 seconds