[MNGSITE-550] What's new in Maven 4?

[Bukama]

This PR adds an article about the major changes in Maven 4.

[Bukama]

Info:

• I put the article quite on high in the menu to make it more visible. When Maven 4 grew up a bit it can be (re-)moved.
• I manually edited the site.xml to not apply full code style changes as it's not correctly formatted as of now (see #MNGSITE-539 Formatting the affected files #595)

[Bukama]

Thanks for the feedback and the editing @gnodet!

[Bukama]

Hope everything is fine now :)

[elharo]

I'm not sure this is true. If it is, elaboration is needed.

[Bukama]

I'm not sure this is true. If it is, elaboration is needed.

@cstamas @gnodet Can you give us some insight please?

[Bukama]

Thank you for your feedback @elharo! Integrated all of your text suggestions and left the two questions/doubts for further responses/discussion - I'm open to everything.

[Bukama]

Consider the audience of this document. This simply is not relevant to someone who simply wants to use Maven to build their code. It's only relevant to the people developing Maven and that's not who this is written for.

I slightly disagree on that: The audience of this document are all Maven users - those who only want to run their build, but also those who want to know more about the changes, are responsible for build management in their teams, etc (I think someone called them "power users"). If we only considers those who "blindly" use Maven, we don't need the article at all. They are those who still run Maven 3.3.9 and mvn clean install because that's what they've read in a tutorial or what was told them years ago.

I'm not sure we can expect people reading this document to already know the difference between build and consumers. This should probably be carefully explained right up front.

What do you think about

Throughout the years, one important rule has been maintaining the highest backward compatibility possible, especially with its [POM-schema with Model version 4.0.0][2].
This is very important, because POM files with this schema version are not only used for the build of the own project.
Projects, using 3rd party libraries, also rely on the POM files of those, as it contains information needed to successfully run their own builds.
Those projects are called "(a dependency) consuming projects".

Also, "consumers" is a strange term here. I might consider dependents instead, but either way it does need to be defined.

Used the term "consumers" due the terms the committers introduced when developing this feature.

[Bukama]

@elharo Thanks for your feedback again. I don't know why I have not seen it 4 days ago :O Think I went through all of them, except the subproject renaming. Might have another look at it tomorrow (I'm too tired for that now).

[slachiewicz]

do You have plan to publish it now or when 4 is released?

[Bukama]

do You have plan to publish it now or when 4 is released?

I would like to release it now, as a) @cstamas said we get asked what changes more often and b) several of us (e.g. Maarten, Karl Heinz, Robert, me) give talks about that quite a long time, but it's always too less time on conferences or many JUG to cover all.

[Bukama]

This huge PR has been stale some time. From time to time someone has comments about minor parts of the article, others have already approved it.
As we can easily update the page when things change (added a note about that), I will merge this PR so the information are visible for the community.