Gradle Extension Plugin: "Configuration with name 'implementation' not found", when setting quarkusExtension.deploymentModule #32767
Comments
quarkus-bot
bot
added
area/gradle
|
/cc @evanchooly (kotlin), @geoand (kotlin), @glefloch, @quarkusio/devtools |
|
When trying to use Quarkus which I have no idea what to do with... |
|
That's really weird, it looks like the java plugin is not correctly applied, this plugin is in charge of registering implementation and annotationProcessor configurations |
|
@glefloch will you have time to look into this one? |
|
If you change the name of the deployment module so that it is lexicographically smaller than the name of the runtime module, e.g. prefix it with an I'm guessing Gradle loads modules in lexicographic order. I guess this is why the Java plugin is not applied as you write @glefloch. This would also explain why it works with the default names |
|
Thanks for the analysis @AndreasPetersen. I will try to handle that in the extension plugin to force the java plugin application regardless of the module names |
|
Any update on this? I'm running into the same problem. |
|
An alternative workaround seems to be to set |
That doesn't seem to be working for me. Whatever I fill in it always looks for a module called deployment.
|
While the above may seem to be true, the code in the deployment module is never actually run, so this doesn't actually work. |
|
I actually just updated the example project, and even when prefixing the deployment module name with I'm not exactly sure why it worked before. Maybe it depends on the computer that you are using to build (I was using a different computer when I had success previously). |
|
Did some more debugging in my own project and when I got the deployment module configured correctly I still get the |
|
You could try to put |
That makes no sense to me. You are saying that the runtime module should point to the runtime module and the deployment module should point to the deployment module? |
|
So, how are we going to solve this issue? Is there somebody who knows how the fix the annotationProcessor issue? This issue is kinda blocking for me at the moment. |
|
@peterfortuin yeah, sorry I said something stupid @AndreasPetersen I forked your project and changed the deploymentModule name in runtime/build.gradle and it works on my end, could you try it as well ? |
|
@Pilpin By changing that you can actually build, but the deployment module is then not used. When I do that I see that all the BuildSteps in my runtime module aren't executed. |
…n with name 'annotationProcessor' not found" problem. fixes quarkusio#32767
|
I was able to fix the "annotationProcessor' not found"-problem by applying the Gradle Java Plugin on the deployment project. I created a pull request for that. Let me know what you think about this approach. Maybe there is a better way. It solves my problem. |
…n with name 'annotationProcessor' not found" problem. fixes quarkusio#32767
…n with name 'annotationProcessor' not found" problem. fixes quarkusio#32767 (cherry picked from commit 9f832ee)
Describe the bug
According to the documentation on the Gradle Quarkus extension plugin, the deployment module name can be set using the
quarkusExtension.deploymentModuleproperty. However, setting this to a non-default value, will result in an error.Expected behavior
It should work
Actual behavior
Any Gradle command will result in the following error:
Leaving the property at the default value, with the module being called something else, produces a warning:
How to Reproduce?
I've created a project here that reproduces the issue.
Any Gradle command will reproduce the issue, e.g.
gradle clean.Output of
uname -aorverMicrosoft Windows [Version 10.0.19044.2604]
Output of
java -versionopenjdk version "17.0.2" 2022-01-18 OpenJDK Runtime Environment Temurin-17.0.2+8 (build 17.0.2+8) OpenJDK 64-Bit Server VM Temurin-17.0.2+8 (build 17.0.2+8, mixed mode, sharing)
GraalVM version (if different from Java)
No response
Quarkus version or git rev
2.16.6
Build tool (ie. output of
mvnw --versionorgradlew --version)Welcome to Gradle 8.1! Here are the highlights of this release: - Stable configuration cache - Experimental Kotlin DSL assignment syntax - Building with Java 20 For more details see https://docs.gradle.org/8.1/release-notes.html ------------------------------------------------------------ Gradle 8.1 ------------------------------------------------------------ Build time: 2023-04-12 12:07:45 UTC Revision: 40ba32cde9d6daf2b92c39376d2758909dd6b813 Kotlin: 1.8.10 Groovy: 3.0.15 Ant: Apache Ant(TM) version 1.10.11 compiled on July 10 2021 JVM: 11.0.17 (Eclipse Adoptium 11.0.17+8) OS: Windows 10 10.0 amd64
Additional information
No response
The text was updated successfully, but these errors were encountered: