Hey Elliotte,
If the project you are referring to is the one that I'm thinking about, the
project I'm working on was in the same situation a couple of years back.
In the last 4 years, we've spent a significant amount of time and resources
to migrate Trino (https://github.com/trinodb/trino) from T
Hey all,
when I gave my talk about Maven 4 some days ago at the Javaland
conference I started with a quick "what Maven version do you use"
question and there were also several hands who use 3.6 and 3.3 (!). I
hope I could convince them to upgrade - so it's the same with Java
versions: There are a
Hi Elliotte,
You mentioned that you are trying to upgrade but it seems the problem is
not updating Maven itself, but updating the Docker images and/or CI
infrastructure, that doesn't look like an issue with Maven, and in any
case, for a legacy project that doesn't care to maintain or update Maven,
Hi,
> On 13. Apr 2024, at 14:05, Slawomir Jaranowski wrote:
>
> Such organizations must have an awareness that support for their product
> can be impossible - especially for free.
> So it looks like large tech companies don't want to pay for maintenance and
> try to require it from an Open Sourc
Hi,
I am afraid that in such legacy projects not only Maven version will be a
problem.
Eg. Most newer versions of popular libraries were switched to JDK 1.8 as
minimum or even higher ... and so on.
Simply if an organization doesn't have time, resources to
regularly maintain their projects, the b
Maybe it should be, but I wanted to drop a note that about a month
after December's decision to require Maven 3.6.3, I shifted onto an
open source project that's been around for 10+ years, is actively
backed by two large tech companies, and still depends on Maven 3.5.x
in the continuous integration
