Geek Answers Handbook

How to make PDE Target Definition Editor display all plugins?

We aim to use Tycho + Eclipse PDE to build OSGi packages in a distributed team.

Until now, artifacts are created and deployed in the Nexus OSS repository. This has been added to support p2 , "artifacts.xml" and "content.xml" are generated (or supplied by Tycho) and correctly enabled by Tycho and p2 Browser .

An invalid link is to add the resulting p2 packet repository to the target platform definition used by the PDE. The PDE Target Editor, apparently, only supports functions or “categorized” plugins , there are no simple packages.

The Tycho repository plugin and the functional packaging of packages independently developed by different partners seem too cumbersome to synchronize. We would like to stick to simple Maven / OBR-like bundle exchanges through one repository.

Is there a way to increase p2 metadata or p2 repository in terms as suggested in this blog , for example. either through the target "tycho-p2-publisher: publish-categories", or by configuring / expanding the "Nexus p2 repository plugin" to make them available for the PDE interface?

This question is related to this question with a hint that the "iu" syntax support is not yet implemented.

+7
nexus eclipse-plugin p2 eclipse-pde tycho
source share
1 answer

Maybe you should try another destination editor. There is an alternative TPD editor / generator from Mikaël Barbero with some useful features:

  • autocomplition
  • version control
  • unifying structure
  • ...
0
source share

More articles:


All Articles