-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OSGi capability namespace for TestEngines #2100
Milestone
Comments
kriegfrj
added a commit
to kriegfrj/junit5
that referenced
this issue
Feb 4, 2021
kriegfrj
added a commit
to kriegfrj/junit5
that referenced
this issue
Feb 4, 2021
kriegfrj
added a commit
to kriegfrj/junit5
that referenced
this issue
Feb 4, 2021
kriegfrj
added a commit
to kriegfrj/junit5
that referenced
this issue
Mar 29, 2021
Team decision: We're okay with adding the metadata. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Pending the resolution of #2095:
I would also like to see us leverage the OSGi capability mechanism in some way to define dependency relationships between test bundles and test engine bundles. That way, the resolver can help with making sure that the correct engines are included in the set of run bundles. For example, the test engine bundle could declare something like this:
...then the test bundle can declare its dependency on a particular versions of particular engines by (eg) the following:
Now the resolver will be able to ensure that the test bundles are paired with the correct versions of the correct test engines. The syntax might need a bit of tweaking (I'm not an expert in this area), but hopefully the idea makes sense.
Deliverables
Provide-Capability
metadata to thejunit-jupiter-engine
andjunit-vintage-engine
OSGi manifests.The text was updated successfully, but these errors were encountered: