This message was deleted.

Never used Scala, but I'd assume it is the same as with any other JVM language. Make

common

a project like the other three and declare a dependency from those three to

common

.

@Vampire I have used the method which mentioned by you. But the issue is. When I try to publish the jar to Mavenlocal (though it published successfully) in the pom and module files which create inside .m2 does contain that common as a dependency which cannot be used. Like this

<dependency>
<groupId>Rootdir.data</groupId>
<artifactId>unspecified<artifactId>
................ 
</dependency>

So is there any method to overcome this issue? I used below code line in build.gradle under dependencies

implementation project(:data:common)

Properly set up publishing for common too and publish common too.

Just to clarity. We cannot achieve it without publishing common also. Isn't it?

You can by some shading, but you shouldn't. If you split it into multiple projects, the clean solution is to also publish those components.

The only issue is we have so many modules and all those may have different types of common functionalities. If I plan to publish it separately the only task would be publishing common modules. That's the reason I try to reduce that difficulty 🙂