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)
2) Participate in the projects you depend on so you are able to provide
the patch in the version you like and having earned enough carma for
some one with release power to release that specific version
3) Pay someone on the project to do so on your behalf (and enter some
kind of customer-releation with that person) especially if special LTS
support is required for specific combinations
Am 06.02.24 um 14:28 schrieb Elliotte Rusty Harold:
On Tue, Feb 6, 2024 at 10:50 AM Kévin Buntrock <kevin.buntr...@gmail.com> 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 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 one bug **and nothing else**. They want a
patch on the old release, not a new release that deprecates 32 methods
and classes, changes the behavior of 5 other methods, and requires
them to recompile their code and update seven other dependencies.
Customers hate being pushed into new versions when they're not ready
to migrate or don't see any personal benefit from the "improvements".
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
