You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The only downside to defining it in `<plugins>` in the parent pom
is that there's a warning when running the plugin on the parent pom:
[INFO] --- bundle:5.1.9:manifest (bundle-manifest) @ commonmark-parent ---
[WARNING] Ignoring project type pom - supportedProjectTypes = [jar, bundle]
The upside is we don't have to remember to put the plugin into all the poms.
The configuration is as recommended here:
https://felix.apache.org/documentation/subprojects/apache-felix-maven-bundle-plugin-bnd.html#_adding_osgi_metadata_to_existing_projects_without_changing_the_packaging_type
Compared to the previous one, the only differences are:
- Import-Package adds imports for java packages, which seems to be recommended,
see bndtools/bnd#2507
- Import-Package of own packages that were exported (e.g. org.commonmark in core)
don't have the version number, not sure what's recommended there
0 commit comments