<project>
<dependencies>
<dependency>
<groupId>com.mysema.querydsl</groupId>
<artifactId>querydsl-apt</artifactId>
<version>${querydsl.version}</version>
<scope>provided</scope>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<configuration>
<excludes>
<exclude>
<groupId>com.mysema.querydsl</groupId>
<artifactId>querydsl-apt</artifactId>
</exclude>
</excludes>
</configuration>
</plugin>
</plugins>
</build>
</project>
I will got a package with querydsl-codegen-3.6.4.jar in its lib-provided directory.
Excludes won't automatically apply to transitive dependencies, you'll need to list everything that you want removed.
Why not? In what scenario one would want child dependencies in their project when they don't want parents? Can there be a flag to exclude it conditionally at least?
Team, you may want to reconsider if the design is appropriate for many of the use cases of the plugin. The current behavior is not totally consistent when using ZIP and MODULE layouts in combination. I am going to use the layout factory feature coming in 1.5 (thanks @wilkinsona for the tip, I appreciate it) but still, I don't think you thought it through.
Most helpful comment
Team, you may want to reconsider if the design is appropriate for many of the use cases of the plugin. The current behavior is not totally consistent when using ZIP and MODULE layouts in combination. I am going to use the layout factory feature coming in 1.5 (thanks @wilkinsona for the tip, I appreciate it) but still, I don't think you thought it through.