> 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 si
On Sun, May 25, 2025, 14:40 Tamás Cservenák wrote:
> > 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,
I believe JPMS has been around for something like 15 years. And after 15
years of pushing it hard, it doesn't seem like it is used by too many people.
If people are not using it by now, how good of an idea is it to push it now? I
feel like the market has spoken (over and over again) on this
I think we need to clarify that
1. Maven 3 plugins should work with Maven 4 (eventually require a recent
update that fixes small compatibility issues),
2. and this is still the main expected way to use plugins with Maven 4
Maven 4 - specific plugins, using the still experimental Maven 4 API, is s
Le 2025-05-25 à 19 h 12, Hunter C Payne a écrit :
My experiences with JPMS have been universally been bad.
Your experience of JPMS, or your experience of Maven 3 / Gradle support
of JPMS?
If you are going to do this, you need to make the default for it to be
completely disabled.
As repe
On Sun, May 25, 2025 at 7:14 PM Hunter C Payne
wrote:
>
> I believe JPMS has been around for something like 15 years. And after 15
> years of pushing it hard, it doesn't seem like it is used by too many people.
Java 9 introduced the Java Platform Module System (JPMS) in September
2017 — just e
On 5/25/25 12:25, Elliotte Rusty Harold wrote:
> On Sat, May 24, 2025 at 7:28 PM John Neffenger wrote:
>> I'm genuinely curious, is there a reason why Maven has not switched to
>> fixed release dates and Java support policies?
>>
>> Every other Java project in which I participate, including the JD
Plugin developers aren’t forced to migrate. I’m using Maven 4 daily and I
don’t use a single plugin that uses the new api.
So while I agree that stability is required, the stability is provided by
the Maven 3 api, mostly supported unchanged in Maven 4.
Le dim. 25 mai 2025 à 12:26, Elliotte Rusty
Le 2025-05-25 à 13 h 28, Elliotte Rusty Harold a écrit :
Can you be more specific? Is there some code we need to produce or
compile that we cannot compile with Java 8?
Yes. Maven 4 core and the compiler plugin 4.0.0-beta already got the
following Java 9+ dependencies:
* MODULE_PATH, UPGRAD
On Sat, May 24, 2025 at 7:28 PM John Neffenger wrote:
>
> I'm genuinely curious, is there a reason why Maven has not switched to
> fixed release dates and Java support policies?
>
> Every other Java project in which I participate, including the JDK
> itself, JavaFX, and NetBeans, switched long ago
On Sat, May 24, 2025 at 1:23 PM Guillaume Nodet wrote:
>
> I don't think they're talking about the Maven 4 API when they expect
> API stability.
> They rather refer to user-facing API such as schema changes, etc...,
> rather than dev-facing API.
Plugin developers need API stability though.
--
E
On Sat, May 24, 2025 at 6:22 PM Martin Desruisseaux
wrote:
> Java 9+ for supporting JPMS. This is needed not only in some plugins
> (compiler, javadoc, maybe surefire), but also in some places of Maven
> core (class-path versus module-path, cache of module-info). Even if not
> everyone is interes
On Sat, May 24, 2025 at 6:27 PM Manfred Moser wrote:
> I also find it amazing that we have to justify and vote for upgrading.
> Why not the inverse ... we always upgrade by default and we do a vote on
> demand only. Then we decide for supporting old, outdated, and hence
> often insecure stuff (ru
Eliotte,
While I sometimes find your hunting and fishing stories
amusing, I also find them very tiresome.
Maven is not a subcontractor or anything like that for any
of the companies you keep talking about. Maven is not
(contractually or in any other way) obliged to "deliver
best experience" or ev
Howdy,
TBH, I _kinda remember_ (may be wrong, it may been only mentioned but
not voted upon - that is the "crux" of ASF projects) that
when we raised Maven 4 to Java 17, it was agreed it will be LTS - 2
(it was 17 at the time of vote).
As for fixed dates, am _really unsure_. We want to get "out"
Jpms is not a topic, you can use jpms and mjars using a makefilr do maven
can be rewritten in go and it would work (otherwise toolchain and java
min+n couldn't work).
Now to be concrete: how to we exit this thread, vote is quite pointless and
will be in loop I fear so we need a way to move forward
+1000 to Tamás comment,
On Sun, May 25, 2025 at 1:52 PM Tamás Cservenák wrote:
>
> Eliotte,
>
> While I sometimes find your hunting and fishing stories
> amusing, I also find them very tiresome.
>
> Maven is not a subcontractor or anything like that for any
> of the companies you keep talking abo
Guillaume Nodet
Le dim. 25 mai 2025 à 13:30, Elliotte Rusty Harold a
écrit :
>
> As much as I would like to rip out Modello and chuck it into the
> Mariana trench, I don't think that's likely to happen.
Why is that so ? If you want to replace it with something else,
18 matches
Mail list logo
