On Mon, 14 Oct 2024 at 09:14, Martin Desruisseaux <martin.desruisse...@geomatys.com> wrote: > > Problem 2: Extra dependencies > > One of my projects depends on java.desktop in testing, but not in > > prod. Since this cannot be expressed in <dependencies>, it cannot be > > automatically derived as described above > > As mentioned in my previous email, it is expressed by a dependency with > <scope>test</scope>. The new compiler plugin already supports that. This > is handled in the same way as any other test dependencies such as JUnit.
So you've defined a GAV for Java modules like java.desktop? > The most productive way to resolve those questions may be to have a > working prototype and checks which issues are still valid on that > prototype. However some issues such as problem 6 are not compiler > issues, but Surefire issues. Do we need to have the full stack tested > before validating the approach? Happy to test - I remain unconvinced that an approach based on command line flags derived from existing Maven info is sufficient. Stephen --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
