maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Lilja <>
Subject Re: proposal for maven-archetype to switch to dom4j 2.1.1 (and Java 8)
Date Mon, 03 Jun 2019 17:47:18 GMT
+1, people on old versions of Java can remain on the old version of the
plugin. No one who is in a project where an old version of Java is still in
use (< 8) expect to have everything else in their eco-system (3PPs, maven
plugins etc) at bleeding edge versions. I guess many such projects are many
versions behind on even supported releases...particularly regarding Maven

- Eric L

On Mon, Jun 3, 2019 at 7:23 PM Mickael Istria <> wrote:

> People who don't want to update are the ones who have to pay the effort,
> not the project that tries to ship a security fix.
> The simplest past forward is the one provided by Tony. Customers who don't
> want to use it can remain on previous version of the archetype plugins.
> Other proposals to fix it are just more time-consuming without providing
> value to Maven project.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message