NOTE: The current preferred location for bug reports is the GitHub issue tracker.
Bug 919 - Add OSGi headers to the htmlparser Jar
Add OSGi headers to the htmlparser Jar
Classification: Unclassified
Component: HTML parser
All All
: P2 normal
Assigned To: Nobody
Depends on:
  Show dependency treegraph
Reported: 2012-04-27 16:15 CEST by Romain Deltour
Modified: 2012-06-08 16:34 CEST (History)
1 user (show)

See Also:

Patch to the POM file (1.87 KB, application/octet-stream)
2012-04-28 01:02 CEST, Romain Deltour

Note You need to log in before you can comment on or make changes to this bug.
Description Romain Deltour 2012-04-27 16:15:40 CEST
It would be much useful for OSGi users if htmlparser was natively distributed as an OSGi bundle. This minimally requires adding some unobtrusive headers to the jar's manifest.

Some tools can help doing that automatically at build time (e.g. "bnd", a tool developed by OSGi's former editor Peter Kriens, available both for Maven or Ant). I volunteer to help if needed and if this feature request is accepted (I know OSGi reasonably well, although I'm not an OSGi "guru").
Comment 1 Romain Deltour 2012-04-28 01:02:17 CEST
Created attachment 217 [details]
Patch to the POM file

Attached is a patch for the POM file found in htmlparser sources.

The modified POM use the packaging type "bundle" along with maven-bundle-plugin to package the project as an OSGi bundle.
Comment 2 Henri Sivonen 2012-05-23 15:48:46 CEST
I have no clue what this does, but I trust it makes sense to Maven users.


Thank you.
Comment 3 Romain Deltour 2012-06-05 16:13:18 CEST
Although the patch went in the POM used to build 1.4, it seems the maven-bundle-plugin is not applied and the resulting Jar does not have OSGi headers.

This may be linked with the workarounds performed as described in bug #921.
Comment 4 Romain Deltour 2012-06-08 16:34:12 CEST
Re-closing. The POM in tag  RELEASE_1_4 and deployed to Maven Central does succeed in adding OSGi headers. The released jar is OK.

Please forget previous comment #3, probably due to uncommitted local changes in my setup.