-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
GraphQL Typesafe client with sources in a dependency #44550
Comments
/cc @jmartisk (graphql), @maxandersen (jbang), @phillip-kruger (graphql), @quarkusio/devtools (jbang) |
What is wired is that in the build log we see entries like that:
So I guess this build step is executed: Lines 219 to 238 in e44e07e
But somehow not available when the quarkus app is starting. |
Does the library contain a |
I added a Jandex index, but no According to https://quarkus.io/guides/cdi-reference#bean_discovery they say:
|
"Content is ignored" means it can be empty :) |
Indeed. I understood the docs https://quarkus.io/guides/cdi-reference#bean_discovery as |
|
@aloubyansky @jmartisk should this issue be re-opened? Given the commit history of my test lib: I have different versions of my test lib Version 0dde568
Does have:
File list in "gitlab-workitem-graphql-client-0dde568aa4.jar"
Version 5964fd4138
Does have:
File list in "gitlab-workitem-graphql-client-0dde568aa4.jar"
My test project (updated to quarkus
So right now I would say that Quarkus requires the I happy to contribute at least a test case if you point me to the place where those should be located, and how you manage those "external libraries" in the test suite (I guess you prefer something either built locally or published on maven central than consuming some random jars from jitpack) |
Then let's have another look, we may be wrongly registering the synthetic bean for the client API... @mskacelik maybe you have some time for this? @jmini As for the tests that you asked, I assume we would simply dynamically build a JAR using ShrinkWrap and add it into the deployment (most tests just build the testing artifact via ShrinkWrap, this one would build two artifacts) |
When having the typesafe client sources (an interface with the
@GraphQLClientApi
annotation and model classes) inside my quarkus project everything works great. I can inject the client like this:See docs: https://quarkus.io/guides/smallrye-graphql-client
Example project for calling the GitLab GraphQL endpoint:
quarkus-graphql-client (on branch
main
commit9b2fcec
)Now I would like to put my sources in a dedicated library:
Example project: gitlab-workitem-graphql-client
Can be loaded with jitpack as:
Gradle config of the quarkus project
Maven config of the quarkus project
Test of the typesafe client outside of quarkus in a simple Jbang script
But when I try to include this library in my quarkus project, It fail during startup.
Example project for calling the GitLab GraphQL endpoint:
quarkus-graphql-client (on branch
external-library
commit1254ebc
)Complete Quarkus App logs
The text was updated successfully, but these errors were encountered: