search

stempler / bnd-platform

Build OSGi bundles and Eclipse Update Sites from existing JARs, e.g. from Maven repositories (Plugin for Gradle)
Apache License 2.0
79 stars 30 forks source link

Is it possible to prevent feature-group in generated update-site #43

Closed Argelbargel closed 6 years ago

Argelbargel commented 6 years ago

I'm adding a plugin to a eclipse rcp based product which comes as a zip-archive. Until shortly, i've used custom gradle-code for adding the jars of my plugin, manipulating the metadata-files and repackaging the application and its update-site. As this was quite error-prone if switched to this plugin.

It works like a charm but i've still got one issue: the generated update-site contains a feature group and i cannot find a way to register this group to the application. The update-mechanism of the applications seems to install any feature (or feature group) which is not installed locally but exists in the update-site.

So after the first start of the application it connects to the update-site, detects the missing group and installs it - ignoring the version of my plugin already packaged with it.

This might be a problem of the update-mechanism of the application but my problem would by easily fixed if i could either prevent the bnd-platform-plugin from creating the superfluos group or knew how to tell the application that it already has the group installed.

So, is there a way to prevent the feature group from being created?

Argelbargel commented 6 years ago

After some more googleing i've found the problem. It is not enough to copy the feature's jar to the applications feature folder. instead this has to be extracted to be detected correctly