| Re: [cdt-dev] P2 Update site and CDT versionning |
Hi Alvaro, Thank for your help and suggestion. But unfortunately I am afraid it can’t help. The main issue I have is I need to fix a few bugs as well as complete an unfinished feature of CDT to support my feature. To do this I patch only 2 plugins of the CDT feature platform. I cannot support the whole CDT platform to support my feature. Thus this mean I need to create a new set of patches for each CDT release. It is not a big deal but at least I would like to be able to have a single update site that could resolve automatically the appropriate versioning of the patched plugins according to the Eclipse release version. It is my understanding that this is not possible with the current P2. Thanks Guy From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Alvaro Sanchez Hi Guy, The latest master branch should still be able to compile with Juno, you can test this by setting your target definitions to e.g. /org.eclipse.cdt.target/cdt-e4.2.target if your specific feature is not able to resolve dependencies you may need to create a modified version of the target definition above pointing to them. The successful compilation will now depend of the dependencies being able to still compile with Juno. So the backwards compatibility depends on the actual features/plug-ins. I hope this helps /Alvaro On Thu, Oct 16, 2014 at 8:02 PM, Guy Bonneau <guy.bonneau@xxxxxxxxxxxx> wrote: I need to patch a CDT plugin to be able to install a feature I have developed for CDT. Unfortunately it is quite an headache since for every CDT release a new patch feature need to be created. The developed feature need to include the patch feature as well and is exported to a P2 update repository. For each CDT release a new P2 update site is created and a new version of the feature with the new CDT patch is exported. So far so good. Now out of curiosity I tried to import the developed feature from the P2 update repository created for Eclipse Luna into Eclipse Juno and the feature was displayed within the Eclipse Install Available Software Dialog. Of course any attempt to install the feature fail since the P2 manager cannot resolve the appropriate plugin version dependencies. The question I have is: it is possible to put some kind of info into the P2 metadata to prevent any display of the feature within the Eclipse Install dialog if the P2 update site doesn’t match the Eclipse release version for which it was build? Thanks Guy
|