Hello Martin, Olivier,
Since I posted on this thread, I have abandoned the idea of integration testing in the same Maven module. Instead, for module X, white-box testing is still done within X/src/test/ and integration testing done in a new and separate module X-blackbox which is also Jigsaw/JPMS modular. This approach is a lot less painful than in-single-module testing. -- Ceki Gülcü Sponsoring SLF4J/logback/reload4j at https://github.com/sponsors/qos-ch On 10/17/2022 1:27 PM, Martin Desruisseaux wrote: > Le 17/10/2022 à 12:33, Olivier Lamy a écrit : > >> I wanted to have some opinions on what sort of configurations we could >> add but this didn't get much attention :) >> (https://issues.apache.org/jira/browse/SUREFIRE-2097) Maybe nobody >> really cares of jpms... >> > On my side I do care a lot about JPMS. But I got the feeling that Maven > model is not well suited to JPMS, which caused me to stop following JPMS > issues on Maven and look for other build solution. > > The difficulty I have with JPMS in Maven is that I would like to break > the "one Maven module = one JPMS module" relationship. Instead I would > like "one Maven module = one compilation unit", i.e. a single call to > javac, javadoc or other java tools, which may itself comprise many JPMS > module. > > Martin > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
