-
Notifications
You must be signed in to change notification settings - Fork 220
fix: properly index otherwise ignored dependency #280
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
Conversation
Fixes #272. The core framework dependency needs to be a runtime dependency so that it gets put in the extension-using application. We also need to index the dependency explicitly because Quarkus doesn't do it automatically (as things might get unruly fast).
Can we have a test, either unit test or integration test for this fix? to ensure the same issue wouldn't happen again later on. |
Yes, definitely. |
Thanks |
113799b
to
6e97452
Compare
7ff7e8d
to
7664b85
Compare
This is needed because we cannot currently use QuarkusUnitTest because of an issue with the kubernetes extension and it's not possible to inject beans in a test using QuarkusProdModeTest. The workaround then is to create a separate app that's started using QuarkusProdModeTest and that exposes some information that we can check over REST about the injected beans to verify that they are indeed properly injected.
7664b85
to
ba20028
Compare
Ready for merge. |
LGTM |
Fixes #272. The core framework dependency needs to be a runtime
dependency so that it gets put in the extension-using application. We
also need to index the dependency explicitly because Quarkus doesn't do
it automatically (as things might get unruly fast).