Closed stefan-ka closed 4 years ago
Is there any way to define the "os", "ws", and "arch" attribute on the "plugin" tags of the generated feature.xml?? This would fix the generated updatesite...
Found a solution. For some reason you have to create an empty bnd configuration, then it works.
Example:
bundle "com.eclipsesource.j2v8:j2v8_macosx_x86_64:4.6.0", {
bnd {}
}
Hi there
I'm having a problem in a project where I want to use your plugin and I was wondering if you have any ideas how to fix this.
A few of my Gradle dependencies are already bundles containing an MANIFEST.MF file. And they conain a Eclipse-PlatformFilter:
These are the dependencies (available through maven central):
Now, the problem is that the filter is respected in the corresponding units in the updatesite, but not in the feature bundle (content.xml). An example:
The unit for one of the libs contains the correct filter in the update site:
The feature group unit on the other hand lists all the libs as required without the filter:
With the generated updatesite it is not possible to install the feature, since the feature requires all of the bundles (no filter defined), but the Eclipse installer cannot find the bundles due to the generated filters in the individual bundles:
From my manual tests, I would say that the problem would be solved if the filters would be generated into the feature group unit as well:
However, I don't know how to produce this output with your plugin.
Any ideas how to fix this? Is there maybe a way to specify the filters if I configure the feature in my Gradle build manually? I'm grateful for any inputs how to work around this issue...