Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Update TCK instructions to get TCK running on either CDI 3.0 or 4.0 #753

Merged
merged 2 commits into from
Sep 15, 2022
Merged

Update TCK instructions to get TCK running on either CDI 3.0 or 4.0 #753

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
49a9f9a
TCK instruction update to get tests running on either CDI 3.0 or 4.0
Emily-Jiang Sep 12, 2022
f94ad61
TCK instruction update to get tests running on either CDI 3.0 or 4.0
Emily-Jiang Sep 12, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion tck/README.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@

= Running the Microprofile Config TCK

Any Microprofile Config 2.0 implementation must pass this test suite. The TCK uses `TestNG` and `Arquillian`.
Any Microprofile Config 3.0 implementation must pass this test suite. The TCK uses `TestNG` and `Arquillian`.

== Hardware Requirements

Expand Down Expand Up @@ -204,3 +204,9 @@ Extension` as shown here:
== Example Implementation Using the TCK
An example of how an implementation might go about integrating the Microprofile-Config TCK into a build
can be found in the https://github.com/apache/geronimo-config[Apache Geronimo Project].

== Getting the tests running on CDI 3.0 and CDI 4.0
The test ConfigPropertiesTest.java relies an behaviour from CDI where an empty beans.xml to make test classes included in the archive CDI beans without the need of bean defining annotations.
However, in CDI 4.0, this behaviour has changed. Therefore, the implementation has to provide an option to make empty beans.xml behave the same as CDI 3.0.
This utilised the feature required by CDI 4.0 specification (For compatibility with CDI versions prior to 4.0, CDI Full products must contain an option that causes an archive with empty beans.xml to be considered an explicit bean archive.).
In Open Liberty, it can be achieved via setting a property.