Hello Gradle community! We provide an open source library that can be used as a starter for microservice development. When upgrading to Gradle 8 the build fails with a lot of error messages of the following type: A problem was found with the configuration of task ':sda-commons-server-auth-testing…

You configured output.resourcesDir = output.classesDirs.singleFile which is a very bad idea. With that you configure tasks with overlapping outputs which has many problems and should be avoided as hell. With that innocent looking configuration you for example configured the processResources and co…

Where can it be seen? If I try to open the major-gradle branch in IJ, it complains that you have an unresolved version conflict for antlr4-runtime. And if I try to just execute the :sda-commons-server-auth-testing:compileTestJava task it complains that it cannot find some libraries needed by the w…

Hej @Vampire ! Thanks for taking the time to look into it! :sunflower: I only tested it locally yesterday. I pushed the changes and created a PR that you can look into. Here’s a pipeline run that contains the described errors. Cheers, Christopher

Well, a bit hard to say as your build is not nicely readable as you use bad-practices like subprojects { ... } and so on, so it is pretty unclear where what is configured, which is just one point of why subprojects { ... } and alike are bad. But the error is definitely true. If you execute gradle …

Well, a bit hard to say as your build is not nicely readable as you use bad-practices like subprojects { ... } and so on, so it is pretty unclear where what is configured, which is just one point of why subprojects { ... } and alike are bad. I’ve also read that the subprojects approach is not rec…

At the moment we still use it because we feel it’s easier to maintain than to spread the logic among different files While it might be cleaner to spread the logic to multiple convention plugins so that you can targetedly apply those and usually it is also easier to maintain and read, you can also…

Yeah, but that information is oooold. :smiley: I think now I just don’t need the beans.xml anymore by configuring Weld appropriately or something like that, don’t have in in mind.

Implicit dependeny to subproject in multi module project

Help/Discuss

christopher-cudennec (Christopher Cudennec) April 26, 2023, 11:00am 8

Thanks again for looking into the issue! It saved us a lot of time.

Funny note in the end:
I found out that we had the sourceSets configuration because of our Weld modules.
Seems like you also ran into that problem a couple of years ago

Cheers,

Christopher

Topic		Replies	Views
Multi-module project phantom dependencies Help/Discuss	1	1257	February 26, 2022
Implicit task dependency with single output Help/Discuss	0	448	October 26, 2021
Task A uses this output of task B without declaring an explicit or implicit dependency Help/Discuss	0	11967	May 11, 2022
Multi-module project with sub-modules with same name Help/Discuss	3	4893	April 28, 2020
Gradle spring subprojects/multimodule Help/Discuss	2	3433	June 15, 2023

Implicit dependeny to subproject in multi module project

Related topics