Implicit dependeny to subproject in multi module project

Help/Discuss
6

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 recommended anymore. At the moment we still use it because we feel it’s easier to maintain than to spread the logic among different files. But I guess that’s probably only true for someone who’s worked with the project a lot :smiley: Thanks for pointing it out!

So somehow you configured the latter to use outputs of the former without having a proper dependency. And following the suggested solutions is usually just symptom treatment, but not an appropriate solution btw.

That’s why I came here. I had the same impression. :smiley:

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.

I try to find a reason why this was configured in the first place. This is a very good explanation why we got the “implicit dependency” message. Thanks for spotting it! :sunflower:

I removed that part of the Gradle setup and was able to build my module! Waiting for the complete build.