> As repeated many times on this mailing list, JPMS is opt-in.
For the sake of Maven users we have to _clearly_ communicate these things:
- Maven4 will try to give "first class citizen" support for JPMS
- BUT, it is opt-in, in a way, if user decides to NOT use JPMS, no
change is needed on user side
In other words, if you don't use JPMS, you can just ignore it, and
just use Maven 4 as you did so far with Maven3.
But, if you do want to use it, it will allow you to fully express your
setup (declaratively), instead as today, where you had to rely on
hacks, some sort of heuristics and a lot of luck ("will it work?") :)
(In general, I always tried (and assumed everyone else is doing the
same) to deliver some Maven "new feature", IF it would in any way
interfere with existing builds to leave it "dormant", in a way that
new feature needs conscious user decision, some config, switch.
whatever to become active. There was ONE exception to this on my side:
the new JDK HTTP transport. But even in this case, we always provide
"escape hatch")
Thanks
T
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
