'compileNative-testJava' not found in Quarkus multi-module project #1981
Labels
Comments
|
The apollo plugin creates a task for each sourceSet and makes From the logs, it looks like there is a |
|
Hi @martinbonnin , Thank you very much for the explanation. I´ve created a demo project where this issue also occurs, hope that helps. |
martinbonnin
added a commit
that referenced
this issue
Oct 16, 2020
At a high level, the main change is that the plugin doesn't try to create a GraphQL source set per Kotlin source set anymore. Instead, there is now a 1:1 mapping between a service and a GraphQL source set. By default, files are are searched under src/main/graphql or src/commonMain/graphql but this is just a convention that can be overriden. Trying to map GraphQL source sets was confusing and created issues like #1981 or special cases for the test source sets where we would end up with duplicate classes in the classpath. Also the schema resolution rules were becoming super complex and hard to maintain. Having one GraphQL service per service is a simple mapping that allows the files/schema resolution rules to be way easier than they used to be, removing the need for schemaPath vs schemaFile, CompilationUnit, ApolloVariant, ...
martinbonnin
added a commit
that referenced
this issue
Oct 18, 2020
At a high level, the main change is that the plugin doesn't try to create a GraphQL source set per Kotlin source set anymore. Instead, there is now a 1:1 mapping between a service and a GraphQL source set. By default, files are are searched under src/main/graphql or src/commonMain/graphql but this is just a convention that can be overriden. Trying to map GraphQL source sets was confusing and created issues like #1981 or special cases for the test source sets where we would end up with duplicate classes in the classpath. Also the schema resolution rules were becoming super complex and hard to maintain. Having one GraphQL service per service is a simple mapping that allows the files/schema resolution rules to be way easier than they used to be, removing the need for schemaPath vs schemaFile, CompilationUnit, ApolloVariant, ...
martinbonnin
added a commit
that referenced
this issue
Oct 20, 2020
* Gradle plugin fall cleanup At a high level, the main change is that the plugin doesn't try to create a GraphQL source set per Kotlin source set anymore. Instead, there is now a 1:1 mapping between a service and a GraphQL source set. By default, files are are searched under src/main/graphql or src/commonMain/graphql but this is just a convention that can be overriden. Trying to map GraphQL source sets was confusing and created issues like #1981 or special cases for the test source sets where we would end up with duplicate classes in the classpath. Also the schema resolution rules were becoming super complex and hard to maintain. Having one GraphQL service per service is a simple mapping that allows the files/schema resolution rules to be way easier than they used to be, removing the need for schemaPath vs schemaFile, CompilationUnit, ApolloVariant, ... * update tests * fix codegen test * add Kdoc * update test fixtures
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
Gradle exception in Quarkus multi module project with apollo-android
Description
I´m trying to get apollo-android working in my multi module project that is based on https://quarkus.io/
in my root build.gradle I´ve added the buildscript as described
In each of my modules that is going to use a GraphQL client I have applied the plugin in my build.gradle
Is this a multi-module issue that this library is having or could it be related to Quarkus?
Version
1.3.0
Exception
The text was updated successfully, but these errors were encountered: