On 05/20/2015 11:47 PM, Jim Klo wrote:
I’d like to be able to dynamically update the
manifest.mf and build.properties of the plugin to include all the
dependencies copied over from other plugins.
I’m wondering if anyone has a recipe they could
share for updating the manifest and build.properties files that
the plugin uses to include the right dependency jars, but retain
all the manually managed export information? Or is this all
crazy-talk?
Your goal seems similar to what's provided by the Eclipse Bundle
Recipes project ( https://github.com/eclipse/ebr ), ie turning Maven
artifacts to p2 artifacts at build-time. So maybe you should be
using EBR for that instead of implementing your own mechanism.
However, you'll have big difficulties to generating a MANIFEST.MF
and making it visible to Tycho dependency resolution in the same
reactor. There are a bunch of reported bugs on this topic, and it's
indeed quite a complicated problem. Here is the EBR-related issue:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=464313
HTH
|