On Fri, Nov 5, 2021 at 7:55 AM Olivier Cailloux
wrote:
> ...
> Armed with this rich information, Maven could auto-generate the module-
> info.java file before compiling the code; auto-generate the alternative
> module-info.java file before compiling and running the tests;
>
...
That's like sayi
Think JPMS is not different from OSGi in terms of requirement (it is more
broken than OSGi and less used only) so not sure why it would pollute the
pom, plus depending how you setup your project you don't use the same thing
so it would hurt maven convention phylosophy IMHO.
So it is good to stick t
Howdy,
Not in vanilla maven, but just FYI:
I think all these benefits (along with boundary checks but Maven not JPMS
sense) are provided by takari lifecycle:
http://takari.io/book/40-lifecycle.html
Thanks
T
On Fri, Nov 5, 2021 at 7:55 AM Olivier Cailloux
wrote:
> Dear Maven developers,
>
> I’d
