Hi folks,
Wanted to offer an one 'end user' data point. For transparency, I run Java
engineering at Microsoft (including supporting Minecraft and LinkedIn
subsidiaries). We're one of the Big Tech Co's that have moved 90%+ of their
Java workloads off Java 8 onto 11+ :-).
I acknowledge we're not
The JVM and JRE don't let you escape out of JPMS. Presumably this is why we
had to redo a bunch of Maven modules for Log4j on the master branch
(unreleased WIP for 3.0).
Gary
On Tue, Feb 6, 2024, 6:43 PM Martin Desruisseaux <
martin.desruisse...@geomatys.com> wrote:
> Le 2024-02-07 à 00 h 37,
Le 2024-02-07 à 00 h 37, Gary Gregory a écrit :
I have no use for JPMS today, I just don't want it to get in the way,
which is impossible since there is no --dont-bother-me-jpms flag...
That option exists at the level of the proposed Maven 4 API and has a
JUnit test [1]. Plugins have the
I have no use for JPMS today, I just don't want it to get in the way, which
is impossible since there is no --dont-bother-me-jpms flag...
Gary
On Tue, Feb 6, 2024, 6:34 PM Martin Desruisseaux <
martin.desruisse...@geomatys.com> wrote:
> Hello
>
> Le 2024-02-06 à 16 h 11, Hunter C Payne a écrit
Hello
Le 2024-02-06 à 16 h 11, Hunter C Payne a écrit :
Nobody wants Jigsaw and the API improvements aren't enough to get
people to upgrade.
I cannot debate on whether a small minority, or a big minority, or a
majority of developers want JPMS (a.k.a. Jigsaw), because I have no data
for
Scala has lousy support and the language is dying mainly because Scala3 seems
like a Kotlin clone (with poor support). The folks that run Scala are
academics and it shows in their marketing and mismanagement of the language.
However, Kotlin is growing and it would be very surprising for me
> Security issues. LTS support is a thing, and not just for JDKs.
Customers really, really want versions of tools and libraries they
don't have to upgrade, but that are supported when something does come
up. And when a security issue does come up, they want a drop in
replacement that fixes that
Le mar. 6 févr. 2024 à 16:12, Hunter C Payne
a écrit :
> There are also license differences between Java 8 and Java 9+. And the
> improvements beyond 8 are not things the market seems to want. Nobody
> wants Jigsaw and the API improvements aren't enough to get people to
> upgrade. Those that
There are also license differences between Java 8 and Java 9+. And the
improvements beyond 8 are not things the market seems to want. Nobody wants
Jigsaw and the API improvements aren't enough to get people to upgrade. Those
that really want new language features use Scala or Kotlin and
While I don't think google-http-java-client is something we can rely on to
decide anything for us for the 10 coming years, similarly not sure that
mono-repo in big companies is actually a thing we should consider as a
first citizen, in particular after the drawbacks big companies got trying
to
Eliotte,
You are missing the topic of this whole thread.
What you wrote in any of your mails is totally unrelated to the thread.
I do feel sorry, or unsure, maybe sympathize with your work issues and
difficulties, but I still cannot understand what all that has to do with
the ASF Maven Project?
On Mon, Feb 5, 2024 at 8:46 PM Benjamin Marwell wrote:
>
> Besides that, most big (tech) companies do not allow unmaintained or
> unsupported software.
How I wish that were true. Unmaintained and unsupported software is
all over the place, in big tech, little tech, enterprise, and my
mother's
On Tue, Feb 6, 2024 at 12:00 PM Tamás Cservenák wrote:
>
> Howdy,
>
> For start, I think Martin assumed the "build time Java requirement for
> Maven4"?
>
> If so, my "vote" would be like:
> * build time: "latest LTS" (fixed at the moment when 4.0.0 GA happens,
> until then we just follow LTS),
I'm interested, how do I become a customer of "apache-maven", I'm not
aware of such thing anyways there are some options:
1) Fork and fix that bug and deploy a new version to your
company-artifact server for the version you are using (maven central is
not a requirement for maven dependencies)
On Tue, Feb 6, 2024 at 10:50 AM Kévin Buntrock wrote:
>
> From my modest point of view : glued to old stack projects do not move at
> all. Why move to a new maven version if the one used works?
>
Security issues. LTS support is a thing, and not just for JDKs.
Customers really, really want
On Tue, Feb 6, 2024 at 8:01 AM Benjamin Marwell wrote:
>
> > we need to think about companies
> that pay for old JDK support
>
> There was a suggestion on slack that companies could provide "dev and
> release manager" for Maven 3 and manage the JDK 8 Maven 3 until they lose
> interest. This
I like all 5 cents
Gary
On Tue, Feb 6, 2024, 7:00 AM Tamás Cservenák wrote:
> Howdy,
>
> For start, I think Martin assumed the "build time Java requirement for
> Maven4"?
>
> If so, my "vote" would be like:
> * build time: "latest LTS" (fixed at the moment when 4.0.0 GA happens,
> until then
Howdy,
For start, I think Martin assumed the "build time Java requirement for
Maven4"?
If so, my "vote" would be like:
* build time: "latest LTS" (fixed at the moment when 4.0.0 GA happens,
until then we just follow LTS), post GA "we adjust to latest LTS on each
minor release (so 4.1, 4.2, etc)"
Personnaly (take it as a vote), I find this a good idea to say:
- 3.x: jdk 8 (whatever someone wants to release some fixes)
- 4.x: jdk 17
On Tue, 6 Feb 2024 at 20:50, Kévin Buntrock wrote:
>
> From my modest point of view : glued to old stack projects do not move at
> all. Why move to a new
>From my modest point of view : glued to old stack projects do not move at
all. Why move to a new maven version if the one used works?
Furthermore, I'm quite impressed by the number of projects starting in java
21 for clients I was considering really shy new adopters. Java 21 is here,
works well,
> we need to think about companies
that pay for old JDK support
There was a suggestion on slack that companies could provide "dev and
release manager" for Maven 3 and manage the JDK 8 Maven 3 until they lose
interest. This already works well for other projects.
Even if no one stands up for
21 matches
Mail list logo
