-
-
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
Add Provide-Capability OSGi header to engine bundles #2544
Conversation
We should also add |
Tentatively slated for 5.8 M1 solely for the purpose of team discussion. |
@kriegfrj Spotless is not happy with the formatting: https://scans.gradle.com/s/zdxufq62y5kri#failure |
920c8a8
to
1d27eac
Compare
Thanks - ran |
1d27eac
to
a537bb7
Compare
I might have to try and recruit @rotty3000 to have a look at the failing verifyOSGi test tasks. The bundles themselves look ok (I think) so it's a problem with the verify task not finding them?
|
I will take a look this week. Thanks for your patience. |
reviewing the issue... |
@kriegfrj You'll laugh when you see what was wrong ;) diff --git a/junit-jupiter-engine/junit-jupiter-engine.gradle.kts b/junit-jupiter-engine/junit-jupiter-engine.gradle.kts
index 0fa4de3259..b11624c6d2 100644
--- a/junit-jupiter-engine/junit-jupiter-engine.gradle.kts
+++ b/junit-jupiter-engine/junit-jupiter-engine.gradle.kts
@@ -32,7 +32,7 @@ tasks {
Provide-Capability:\
org.junit.platform.engine;\
org.junit.platform.engine='junit-jupiter';\
- version:Version=${project.version}
+ version:Version="${'$'}{version_cleanup;${project.version}}"
""")
}
}
diff --git a/junit-vintage-engine/junit-vintage-engine.gradle.kts b/junit-vintage-engine/junit-vintage-engine.gradle.kts
index 8546e232cb..1621a9c65c 100644
--- a/junit-vintage-engine/junit-vintage-engine.gradle.kts
+++ b/junit-vintage-engine/junit-vintage-engine.gradle.kts
@@ -60,7 +60,7 @@ tasks {
Provide-Capability:\
org.junit.platform.engine;\
org.junit.platform.engine='junit-vintage';\
- version:Version=${project.version}
+ version:Version="${'$'}{version_cleanup;${project.version}}"
""")
}
} |
a537bb7
to
c8f89e3
Compare
:laugh: So @rotty3000 wins the quote-of-the-week award. @marcphilipp , I think this one is ready for review/ merge. |
@kriegfrj Could you please rebase this on |
I've done so myself and pushed your commit to |
So sorry, slipped off the radar. Thank you for taking care of it! |
What this means is that merely by consuming the Jupiter client APIs results in requiring a fully fleshed out runtime including launcher as follows - junit-jupiter-api & junit-jupiter-params depend on junit-platform-commons - junit-platform-commons Requires a org.junit.platform.engine=* - junit-jupiter-engine Provides org.junit.platform.engine=junit-jupiter - junit-vintage-engine Provides org.junit.platform.engine=junit-vintage - junit-jupiter-engine & junit-vintage-engine Requires org.junit.platform.launcher=junit-platform-launcher - junit-platform-launcher Provides org.junit.platform.launcher=junit-platform-launcher The solution is solvable having either junit-jupiter OR junit-vintage on your test classpath Signed-off-by: Raymond Augé <raymond.auge@liferay.com>
What this means is that merely by consuming the Jupiter client APIs results in requiring a fully fleshed out runtime including launcher as follows - junit-jupiter-api & junit-jupiter-params depend on junit-platform-commons - junit-platform-commons Requires a org.junit.platform.engine=* - junit-jupiter-engine Provides org.junit.platform.engine=junit-jupiter - junit-vintage-engine Provides org.junit.platform.engine=junit-vintage - junit-jupiter-engine & junit-vintage-engine Requires org.junit.platform.launcher=junit-platform-launcher - junit-platform-launcher Provides org.junit.platform.launcher=junit-platform-launcher The solution is solvable having either junit-jupiter OR junit-vintage on your test classpath Signed-off-by: Raymond Augé <raymond.auge@liferay.com>
What this means is that merely by consuming the Jupiter client APIs results in requiring a fully fleshed out runtime including launcher as follows - junit-jupiter-api & junit-jupiter-params depend on junit-platform-commons - junit-platform-commons Requires a org.junit.platform.engine=* - junit-jupiter-engine Provides org.junit.platform.engine=junit-jupiter - junit-vintage-engine Provides org.junit.platform.engine=junit-vintage - junit-jupiter-engine & junit-vintage-engine Requires org.junit.platform.launcher=junit-platform-launcher - junit-platform-launcher Provides org.junit.platform.launcher=junit-platform-launcher The solution is solvable having either junit-jupiter OR junit-vintage on your test classpath Signed-off-by: Raymond Augé <raymond.auge@liferay.com>
What this means is that merely by consuming the Jupiter client APIs results in requiring a fully fleshed out runtime including launcher as follows - junit-jupiter-api & junit-jupiter-params Requires a org.junit.platform.engine=junit-jupiter - junit-jupiter-engine Provides org.junit.platform.engine=junit-jupiter - junit-vintage-engine Provides org.junit.platform.engine=junit-vintage - junit-jupiter-engine & junit-vintage-engine Requires org.junit.platform.launcher=junit-platform-launcher - junit-platform-launcher Provides org.junit.platform.launcher=junit-platform-launcher The solution is solvable by consuming junit-jupiter-api & junit-jupiter-params in your tests OR in the case of vintage having @requirement(namespace = "org.junit.platform.engine", name = "junit-vintage") Signed-off-by: Raymond Augé <raymond.auge@liferay.com>
What this means is that merely by consuming the Jupiter client APIs results in requiring a fully fleshed out runtime including launcher as follows - junit-jupiter-api & junit-jupiter-params Requires a org.junit.platform.engine=junit-jupiter - junit-jupiter-engine Provides org.junit.platform.engine=junit-jupiter - junit-vintage-engine Provides org.junit.platform.engine=junit-vintage - junit-jupiter-engine & junit-vintage-engine Requires org.junit.platform.launcher=junit-platform-launcher - junit-platform-launcher Provides org.junit.platform.launcher=junit-platform-launcher The solution is solvable by consuming junit-jupiter-api & junit-jupiter-params in your tests OR in the case of vintage having @requirement(namespace = "org.junit.platform.engine", name = "junit-vintage") Signed-off-by: Raymond Augé <raymond.auge@liferay.com>
What this means is that merely by consuming the Jupiter client APIs results in requiring a fully fleshed out runtime including launcher as follows - junit-jupiter-api & junit-jupiter-params Requires a org.junit.platform.engine=junit-jupiter - junit-jupiter-engine Provides org.junit.platform.engine=junit-jupiter - junit-vintage-engine Provides org.junit.platform.engine=junit-vintage - junit-jupiter-engine & junit-vintage-engine Requires org.junit.platform.launcher=junit-platform-launcher - junit-platform-launcher Provides org.junit.platform.launcher=junit-platform-launcher The solution is solvable by consuming junit-jupiter-api & junit-jupiter-params in your tests OR in the case of vintage having @requirement(namespace = "org.junit.platform.engine", name = "junit-vintage") Signed-off-by: Raymond Augé <raymond.auge@liferay.com>
What this means is that merely by consuming the Jupiter client APIs results in requiring a fully fleshed out runtime including launcher as follows - junit-jupiter-api & junit-jupiter-params Requires a org.junit.platform.engine=junit-jupiter - junit-jupiter-engine Provides org.junit.platform.engine=junit-jupiter - junit-vintage-engine Provides org.junit.platform.engine=junit-vintage - junit-jupiter-engine & junit-vintage-engine Requires org.junit.platform.launcher=junit-platform-launcher - junit-platform-launcher Provides org.junit.platform.launcher=junit-platform-launcher The solution is solvable by consuming junit-jupiter-api & junit-jupiter-params in your tests OR in the case of vintage having @requirement(namespace = "org.junit.platform.engine", name = "junit-vintage") Signed-off-by: Raymond Augé <raymond.auge@liferay.com>
What this means is that merely by consuming the Jupiter client APIs results in requiring a fully fleshed out runtime including launcher as follows - junit-jupiter-api & junit-jupiter-params Requires a org.junit.platform.engine=junit-jupiter - junit-jupiter-engine Provides org.junit.platform.engine=junit-jupiter - junit-vintage-engine Provides org.junit.platform.engine=junit-vintage - junit-jupiter-engine & junit-vintage-engine Requires org.junit.platform.launcher=junit-platform-launcher - junit-platform-launcher Provides org.junit.platform.launcher=junit-platform-launcher The solution is solvable by consuming junit-jupiter-api & junit-jupiter-params in your tests OR in the case of vintage having @requirement(namespace = "org.junit.platform.engine", name = "junit-vintage") Signed-off-by: Raymond Augé <raymond.auge@liferay.com>
What this means is that merely by consuming the Jupiter client APIs results in requiring a fully fleshed out runtime including launcher as follows - junit-jupiter-api & junit-jupiter-params Requires a org.junit.platform.engine=junit-jupiter - junit-jupiter-engine Provides org.junit.platform.engine=junit-jupiter - junit-vintage-engine Provides org.junit.platform.engine=junit-vintage - junit-jupiter-engine & junit-vintage-engine Requires org.junit.platform.launcher=junit-platform-launcher - junit-platform-launcher Provides org.junit.platform.launcher=junit-platform-launcher The solution is solvable by consuming junit-jupiter-api & junit-jupiter-params in your tests OR in the case of vintage having @requirement(namespace = "org.junit.platform.engine", name = "junit-vintage") Signed-off-by: Raymond Augé <raymond.auge@liferay.com>
Adds
Provide-Capability: org.junit.platform.engine;org.junit.platform.engine=junit-vintage;version:Version="${project.version}"
tojunit-vintage-engine
Provide-Capability: org.junit.platform.engine;org.junit.platform.engine=junit-jupiter;version:Version="${project.version}"
tojunit-jupiter-engine
Fixes #2100.
I hereby agree to the terms of the JUnit Contributor License Agreement.