-
Notifications
You must be signed in to change notification settings - Fork 83
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
Make ModelConstructionTest, OASFactoryErrorTest activate OpenAPI #657
Conversation
Can one of the admins verify this patch? |
@eclipse-microprofile-bot test this please |
I just want to test this against smallrye and OpenLiberty before I merge it. |
Thanks for reviewing this! I would primarily need this in the 3.1 stream. There is currently no branch for 3.1, so I can't open a PR. Is there any chance that 3.1.2 release could be made? |
We can probably back-port to 3.1.2. I'll create a branch in history for 3.1.x |
Thanks! I created the 3.1.x PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change does not cause any issues for smallrye-open-api 4.0.0-prerelease.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doesn't cause any issues on OpenLiberty either.
Proposal to resolve #655
After reading #413, I believe these two tests should not be using empty deployment.
OpenAPI should be somehow activated, for the tested functionality to be correctly initialized. The app container have no reason to do this initialization if there is nothing that suggests OpenAPI endpoint is needed.
Currently in Wildfly, these tests only pass if they happen to run after another test from the OpenAPI TCK, where the other test activates OpenAPI for them. They fail if run alone, or if they happen to run as the first test in the module.