Hi,
I am in the process of modularizing one of my projects and hit some
rather annoying limitations that I thought needed changes to my Maven
build and dependencies due to the way the Java module system works, but
it turned out that this is by design and there is a way out. Alan
Bateman suggested that I should use --add-modules to add runtime scoped
dependencies to my tests and it works like a charm:
https://mail.openjdk.java.net/pipermail/jigsaw-dev/2021-June/014679.html
Now my question is, why does the maven-surefire-plugin not add this flag
by default, with a possible option to disable the behavior?
Has this been considered/discussed before? I couldn't find anything on
the internet yet. I am adding the necessary bits now through
<argLine></argLine> to avoid having to use the compile scope and listing
the modules in the module-info descriptor, but I would prefer if the
surefire team would add support for this out of the box.
What do you think?
Regards,
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
