A flexible way to set poms versions, multi-modules projects included, is Versions Maven Plugin. mvn versions:set -DnewVersion=your_new_version It will adjust all pom versions, parent versions and children versions in a multi-module project. then mvn versions:commit or mvn versions:revert
I’d create one additional “base” module (project), packaging “jar”, that contains the common resources in src/main/resources. Then I’d make the other modules depend on that project. Now they see the common resources on their classpaths.
In case anybody comes back to this, I think the problem here was failing to install the parent pom first, which all these submodules depend on, so the Maven Reactor can’t collect the necessary dependencies to build the submodule. So from the root directory (here D:\luna_workspace\empire_club\empirecl) it probably just needs a: mvn clean install (Aside: … Read more
Quarkus automatically indexes the main module but, when you have additional modules containing CDI beans, entities, objects serialized as JSON, you need to explicitly index them. There are a couple of different (easy to implement) options to do so. Using the Jandex Maven plugin Add the following to the pom.xml of the module you want … Read more
You should try to use ${databasedriver} directly in your child pom.
Just found the solution. Instead of defining base packages to scan from separate library, I’ve just created configuration class inside this library with whole bunch of annotation and imported it to my main MyApplication.class: package runnableProject.application; import com.myProject.customLibrary.configuration.SharedConfigurationReference.class @SpringBootApplication @Import(SharedConfigurationReference.class) public class MyApplication { public static void main(String[] args) { SpringApplication.run(MyApplication.class, args); } } package … Read more
Just add this to build gradle file to avoid the issues related NonExistentClass kapt { correctErrorTypes true } https://kotlinlang.org/docs/reference/kapt.html#non-existent-type-correction
Not entirely sure which of these you’re after, but they should cover your bases. 1. Calling the tasks directly You should just be able to call gradle :other/projC:hello :other/projD:hello I tested this with: # Root/build.gradle allprojects { task hello << { task -> println “$task.project.name” } } and # Root/settings.gradle include ‘projA’ include ‘projB’ include … Read more
The build order is determined by the Maven reactor which is a mechanism that automatically ensures correct build order for multimodule builds by sorting the projects. See the official documentation for how it works. It says: The following relationships are honoured when sorting projects: a project dependency on another module in the build a plugin … Read more