This message was deleted Gradle Community #community-support

Join Slack

This message was deleted.

# community-support

Slackbot

01/10/2023, 9:22 AM

This message was deleted.

Vampire

01/10/2023, 9:28 AM

Sure, just make a multi-project build with one project per module

Alessandro Parisi

01/10/2023, 9:31 AM

I tried something like this: I have a modules subdirectory, each module has a build.gradle Modules are included like this:

Copy code

include 'backend'
include 'frontend'

project(':backend').projectDir = file('modules/backend')
project(':frontend').projectDir = file('modules/frontend')

Modules are imported correctly, but when I add a module-info it says that dependency modules cannot be found

Vampire

01/10/2023, 9:32 AM

What you showed is correct. Can you provide an MCVE?

Alessandro Parisi

01/10/2023, 9:33 AM

Yes, let me create a sample project and I'll report back

👌 1

Alessandro Parisi

01/10/2023, 9:43 AM

Here's the MCVE:

Alessandro Parisi

01/10/2023, 9:44 AM

The project is configured to fail To make it work simply delete the module-info file in the backend module

Vampire

01/10/2023, 9:50 AM

Those dependencies you use are neither full modules, nor have an automatic module name in the manifest, so Gradle puts them on the classpath, not the modulepath.

Vampire

01/10/2023, 9:51 AM

See this for further information: https://discuss.gradle.org/t/automatic-modules-jigsaw-and-gradle/44431

Alessandro Parisi

01/10/2023, 9:52 AM

So it's their fault? What bad luck lol, I have 2 dependencies and both have the same issues haha

Vampire

01/10/2023, 9:52 AM

"fault" is too hard. They are just not prepared for JPMS.

Vampire

01/10/2023, 9:54 AM

Btw. please do not use the

-all

distribution. There is only one specific use-case where it is useful. When using Groovy DSL build scripts (I'd recommend to use Kotlin DSL anyway) and only while actually editing the build scripts. In all other situations you are just wasting the time, bandwidth and disk space of everyone and everything just executing the build.

Alessandro Parisi

01/10/2023, 9:57 AM

I was using the

-all

distribution thinking that it included the sources needed to the IDE to show the quick documentation, I see it works anyway, I was wrong Will switch to

-bin

, thank you very much!

Vampire

01/10/2023, 10:00 AM

As I said, while editing the build script in Groovy DSL it is indeed useful to have the sources and maybe docs. But only while actually editing. Use Kotlin DSL then your life improves and there is also no need for

-all

anymore at all.

Open in Slack

Previous Next