Hi Benjamin,

I'm especially interested in the previous major bumps, not the current one.
For Maven 4 we have 3 hours to go into the details.

We will mention the new Java Runtime version requirement, but I consider that a 
change that lifts upon the real majors.
During both Maven2 and Maven3 the Java runtime version requirement has 
increased.
In general that was not a real issue as it was a push to the latest EOL version.

Thanks,
Robert

-----Original Message-----
From: Benjamin Marwell <bmarw...@apache.org> 
Sent: woensdag 25 september 2024 21:04
To: Maven Developers List <dev@maven.apache.org>
Subject: Re: Most significant changes in history with every major release of 
Maven

I think skipping 9 Java versions between Maven 3 and 4 is a big deal and has 
never happened before 😁

Java 17 will be required for Maven 4.

Also Maven 4: extensions where you can use pom.conf or pom.yml etc.

On Mon, 23 Sept 2024, 10:53 Robert Scholte, <rfscho...@apache.org> wrote:

> Hi all,
>
>
>
> Within 2 weeks I will do a talk with Maarten about Maven 4.
>
> Part of that are some slides about previous major releases that should 
> clearly explain why it was a major release at not the next minor.
>
>
>
> In short I came with this list:
>
>
>
> M1 -> M2: (breaking change, migration required)
>
>               modelVersion: 3.0.0  -> 4.0.0
>
>               xsd: https://maven.apache.org/xsd/maven-v3_0_0.xsd -> 
> https://maven.apache.org/xsd/maven-4.0.0.xsd
>
>               (as doc):
>
> https://maven.apache.org/archives/maven-1.x/reference/maven-model/3.0.
> 2/mave
> n.html
> <https://maven.apache.org/archives/maven-1.x/reference/maven-model/3.0
> .2/maven.html>
> -> https://maven.apache.org/ref/3.9.9/maven-model/maven.html
>
>               Spod: project.xml -> pom.xml
>
>               plugin: written in Jelly (=executable XML) -> written in 
> Java
>
>               repository layout:
> /repository/maven/jars/maven-1.0-beta-8.jar
> -> /repository/org/apache/maven/maven-core/2.2.1/maven-core-2.2.1.jar
>
>               introduction of lifecycles
>
> M2->M3: (migration required for reporting plugins)
>
>               Extract dependency/artifact related code to separate 
> independent library: Aether
>
>               Extract maven-reporting to separate independent  library:
> maven-reporting-api + maven-reporting-impl
>
>               Maven-reactor-plugin -> embedded
> (https://maven.apache.org/plugins/maven-reactor-plugin/index.html)
>
> (for the end-user most changes were invisible, as they were mainly 
> under the
> hood)
>
>
>
> Did I miss something important and are these statements correct?
>
>
>
> Thanks,
>
> Robert
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to