biz.aQute.tester.junit-platform conflicts with Junit 6

[holgerfriedrich]

Junit 6 changed the versioning scheme for the junit-platform packages to be in sync with junit-jupiter, i.e. from 1.x to 6.x.
https://github.com/junit-team/junit-framework/wiki/Upgrading-to-JUnit-6.0#new-versioning-scheme

This conflicts with the requirement <2.0.0 in bnd-resolver-maven-plugin.

[ERROR] Failed to execute goal biz.aQute.bnd:bnd-resolver-maven-plugin:7.2.1:resolve (default) on project org.openhab.core.automation.tests: Unable to resolve <<INITIAL>>: missing requirement osgi.identity;filter:='(osgi.identity=biz.aQute.tester.junit-platform)' [caused by: Unable to resolve biz.aQute.tester.junit-platform version=7.2.1.202601121903: missing requirement osgi.wiring.package;filter:='(&(osgi.wiring.package=org.junit.platform.engine)(version>=1.10.0)(!(version>=2.0.0)))';osgi.wiring.package='org.junit.platform.engine'] 

Not sure if there are technical reasons not to allow Junit 6.
In case it is unnecessary, this restriction should be removed in next patch release.

[chrisrueger]

Thanks for the report @holgerfriedrich
I created #7054 to enlarge the version range to include 6. Please have a look if the import-package looks right to you.

That being said: I don't know if JUnit6 will work. Nobody has tested it and given the history it was pain to even go from JUnit 5.12.2 to above which was just added recently.

If you could help testing I could merge this to master and you could try with the next 7.3.0-SNAPSHOT.

[scordio]

I've seen the same behavior in AssertJ – happy to give it a try once the fix is available as a snapshot!

[chrisrueger]

I added a comment in #7054 (comment)
I think just expanding the range to include 6 is not enough. JUnit6 has changed OSGi headers drastically to deprecate lot of stuff. This makes biz.aQute.tester.junit-platform not resolve with JUnit6 in its current form.