Good morning,
over two months ago I created the PR about "What's new in Maven 4". It
has been stale since about a month now and I feel a bit lost how to
continue with it.
During the PR discussion I created one follow up issue [1] to clearly
define and describe top, root, and base directories, session and
directory properties as it turned out that those are not clearly
described in the documentation yet.

On January 5th, Sylwester asked, if I want to release it now or wait
until release of Maven 4.  Aside from the follow up mentioned before, I
do think the page is good to serve people who are interesting what will
change. That was the starting point for the PR, based on a Slack message
by Tamas, asking if someone can write the changes down. Also the talks I
give on that topic have a lot of listeners. However, from comments in
other discussions I got the _feeling_ (I don't know if this is true)
that some don't want to publish Maven 4 things, until Maven 4 final
version is released.

So I was thinking about how to move on with the PR: Shall I add a note
at the start of the article clearly mentioned that current state is RC2
and the article will get updated (at least) until Maven 4.0.0 is
released? Would this okay for all to get this (really large) PR done?

Matthias


[1] https://github.com/apache/maven-site/issues/651

Am 22.01.2025 um 16:25 schrieb Tamás Cservenák:
Howdy,

Lately, we get this question quite often.

Today Guillaume assembled this very informative presentation:
https://gnodet.github.io/maven4-presentation/

There is also ongoing effort to assemble a page on Maven site as well:
https://github.com/apache/maven-site/pull/598

Have fun
T

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


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

Reply via email to