(maven-site) branch master updated: Improve display of quote in Whats new in Maven 4 article

[mbuenger]

This is an automated email from the ASF dual-hosted git repository.

mbuenger pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git


The following commit(s) were added to refs/heads/master by this push:
     new e20cd546 Improve display of quote in Whats new in Maven 4 article
e20cd546 is described below

commit e20cd5467185ccd22305d202db19ed37cf7af055
Author: Maarten Mulders <mthmuld...@users.noreply.github.com>
AuthorDate: Fri Mar 21 13:15:57 2025 +0100

    Improve display of quote in Whats new in Maven 4 article
---
 content/markdown/whatsnewinmaven4.md | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/content/markdown/whatsnewinmaven4.md 
b/content/markdown/whatsnewinmaven4.md
index 95bab207..e9389f21 100644
--- a/content/markdown/whatsnewinmaven4.md
+++ b/content/markdown/whatsnewinmaven4.md
@@ -43,10 +43,9 @@ Thus, any change in the POM's schema forces each participant 
of the ecosystem to
 support.
 Thus, the Maven POM syntax became fixed, unable to change.
 
-> "With the Maven build schema preserved in amber, we can’t evolve much: we’ll 
stay forever with Maven 3 minor releases,
+> "With the Maven build schema preserved in amber, we can’t evolve much: we’ll 
stay forever with Maven 3 minor releases, unable to implement improvements that 
we imagine will require seriously updating the POM schema…"
 >
->> unable to implement improvements that we imagine will require seriously 
updating the POM schema…"
->> &mdash; <cite>[Hervé Boutemy (in Javaadvent 2021)][1]</cite>
+> &mdash; <cite>[Hervé Boutemy (in Javaadvent 2021)][1]</cite>
 
 In order for Maven to evolve, it's necessary to separate the information 
needed for the build from the information
 needed by the consumers, but without breaking the ecosystem.