build(deps): bump org.apache.felix:maven-bundle-plugin from 6.0.2 to 6.1.0 - #2786
build(deps): bump org.apache.felix:maven-bundle-plugin from 6.0.2 to 6.1.0#2786dependabot[bot] wants to merge 2 commits into
Conversation
Bumps org.apache.felix:maven-bundle-plugin from 6.0.2 to 6.1.0. --- updated-dependencies: - dependency-name: org.apache.felix:maven-bundle-plugin dependency-version: 6.1.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
maven-bundle-plugin 6.1.0 ships bnd 7.3.0. bnd >= 7.2.0 truncates Import-Service filter attribute values at the first '=', which corrupts the blueprint NamespaceHandler service filter and makes the generated manifest unparseable at resolution time (IllegalArgumentException: Unknown operator), failing ConfigExampleTest.testBlueprint. Override the plugin's bndlib dependency back to 7.1.0 (last good release) so the 6.1.0 bump can land until the regression is fixed upstream.
|
@jbonofre Do you know if there is an issue reported in the bndtools repo for this? I did a quick search, but could not find it. |
|
No I don't think there is any issue yet. I plan to create one. |
|
lets see if bndtools upgrade to 7.4.0 changed something.... I don't want to drop your commit by issuing a re-create, so lets check there: |
|
Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry! If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request |
1 similar comment
|
Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry! If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request |
|
I have looked deeper into this issue. @jbonofre already analzyed it:
This still holds. We have now tried several versions:
My proposal is to close this until the bug is fixed in bndtools. |
Bumps org.apache.felix:maven-bundle-plugin from 6.0.2 to 6.1.0.
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)