Le vendredi 05 novembre 2021 à 10:01 +0100, Christian Stein a écrit :
> Or as Robert expressed it:
> https://stackoverflow.com/a/43213506/1431016
> Also read his article linked in the answer.
Thank you, I wish I had seen this article sooner
(https://www.sitepoint.com/maven-cannot-generate-module-
Le vendredi 05 novembre 2021 à 09:27 +0100, Romain Manni-Bucau a
écrit :
> 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 sam
Le vendredi 05 novembre 2021 à 09:12 +0100, Tamás Cservenák a écrit :
> 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:
Thank you for this pointer. The “enforcing dependency usage” part
(http
Dear Maven developers,
I’d like to propose an idea for Maven to help its users better with the
JPMS.
= Goals
As a developer, I’d like to have all the following benefits. It seems
to me that no existing approach provide them all. I assume a single-
module project with some main code and some white
