[GRADLE-2346] Run Bnd verifier on the generated Osgi manifest Created: 12/Jun/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-rc-3
Fix Version/s: None

Type: Improvement
Reporter: Detelin Yordanov Assignee: Unassigned
Resolution: Won't Fix Votes: 0


At the moment the Gradle Osgi plugin does not perform any validation on the generated Osgi manifest, thus it is very easy to generate a manifest that is not valid according to Osgi spec. The Bnd library provides a aQute.lib.osgi.Verifier class that runs some validation on the manifest and generates warning/errors that could be printed to the user.

The Bnd verifier needs to be configured with some settings of the Bnd Analyzer, but the latter is not exposed by the DefaultOsgiManifest therefore it might be required to implement this as part of the DefaultOsgiManifest class (or in a new manifest generation task if such is implemented as part of GRADLE-2268).
Here is a piece of code that runs the Bnd Verifier on the generated manifest:

Verifier verifier = new Verifier(analyzer.getJar(),analyzer.getProperties())
verifier.setClassSpace(analyzer.getClassspace(), analyzer.getContained(), analyzer.getReferred(), analyzer.getUses())


for (String error : verifier.getErrors())

{ logger.error(error) }

for (String warning : verifier.getWarnings()

{ logger.warn(warning) }

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

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