How can I achieve Live-Reload in nested project-structures (maven-multimodule)?
Here's the nonworking example:
Live Reload is not triggered bei changes in demo-lib
or demo-core
while running demo-service
Nonworking Example
<project xmlns=".0.0" xmlns:xsi="; xsi:schemaLocation=".0.0 .0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>com.example</groupId>
<artifactId>multimoduleexample</artifactId>
<version>1.0-SNAPSHOT</version>
<packaging>pom</packaging>
<modules>
<module>services/demo-service</module>
<module>shared/demo-core</module>
<module>libraries/demo-lib</module>
</modules>
<properties>
<mavenpiler.source>21</mavenpiler.source>
<mavenpiler.target>21</mavenpiler.target>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<quarkus.version>3.17.5</quarkus.version>
</properties>
<build>
<plugins>
<plugin>
<groupId>io.quarkus</groupId>
<artifactId>quarkus-maven-plugin</artifactId>
<version>${quarkus.version}</version>
</plugin>
</plugins>
</build>
</project>
Is Hot-Reload in such structure possible, even when the sub-projects have different parent POMs?
I tried Live-Reload in a multimodule-setup and it works awesome when the modules are located in the same directory. When the modules are located in subdirectories, it does not live reload.