[GRADLE-3487] OSGI plugin does not generate import package attributes when the package is available in multiple bundles Created: 16/Jun/16  Updated: 25/Jan/17  Resolved: 16/Jun/16

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: 3.0-milestone-2, 3.0-rc-2

Type: Bug
Reporter: Benjamin Muschko Assignee: Benjamin Muschko
Resolution: Fixed Votes: 0

Known Issue Of:


With the upgrade of our build system from gradle 2.3 to 2.13 we noticed that it no longer generates import package attributes when the package is available in multiple bundles.
We are building bundles that reference the org.eclipse.core.runtime package which is available in both org.eclipse.osgi and org.eclipse.equinox.common bundles on the classpath.
The org.eclipse.osgi bundle does not export the package but contains it, while the org.eclipse.equinox.common is exporting it with version and mandatory attributes.
If Bnd processes the org.eclipse.osgi bundle first, then the package attributes are missing in our bundle, i.e. we get:

Import-Package: org.eclipse.core.runtime

while with previous version (Bnd 2.1) we used to get:

Import-Package: org.eclipse.core.runtime;version="[3.5,4)";common=split

We have reported the issue in Bnd project:


Do you have plans to update to latest bnd in 2.14?

Comment by Benjamin Muschko [ 16/Jun/16 ]

Gradle 3.0-M2 upgraded the BND library to version 3.2.0.

Generated at Wed Jun 30 12:50:04 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.