build(deps): bump org.apache.felix:maven-bundle-plugin from 6.0.2 to 6.1.2 - #2874
dependabot[bot] wants to merge 2 commits into
Conversation
Bumps org.apache.felix:maven-bundle-plugin from 6.0.2 to 6.1.2. --- updated-dependencies: - dependency-name: org.apache.felix:maven-bundle-plugin dependency-version: 6.1.2 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Test Results 705 files ±0 705 suites ±0 1h 19m 19s ⏱️ + 2m 59s For more details on these errors, see this check. Results for commit dab1a08. ± Comparison against base commit 327ea0d. ♻️ This comment has been updated with latest results. |
|
@holgerfriedrich I will push a fix directly on this PR. I'm working on it. |
…orruption maven-bundle-plugin 6.1.2 pulls in bnd 7.3.0. Starting with bnd 7.2.0, the Import-Service header generated for Aries Blueprint namespace handlers gets corrupted, e.g. "filter=(osgi.service.blueprint.namespace=http://...)" becomes "filter=\"(osgi.service.blueprint.namespace\"". This breaks OSGi resolution of any bundle using the Blueprint cm namespace with "Unknown operator" thrown from Felix's SimpleFilter parser, which is why ConfigExampleTest fails in CI. Verified this is a bnd regression (not maven-bundle-plugin) by bisecting bndlib versions: 7.1.0 produces a correct header, 7.2.0 does not, and the corruption is still present in the latest bndlib release (7.4.0). Pinning the plugin's bndlib dependency to 7.1.0 restores the correct manifest while still picking up the maven-bundle-plugin 6.1.2 bump.
|
I spent some time on this and finally gave up, see #2786. |
|
@holgerfriedrich I think the easiest way is to fix in bnd/felix. I will work on it (as Felix PMC member 😄 ). |
|
A newer version of org.apache.felix:maven-bundle-plugin exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged. |
Bumps org.apache.felix:maven-bundle-plugin from 6.0.2 to 6.1.2.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)