Bukama commented on code in PR #598: URL: https://github.com/apache/maven-site/pull/598#discussion_r1896754735
########## content/markdown/whatsnewinmaven4.md: ########## @@ -0,0 +1,474 @@ +# What's New in Maven 4? + +Maven is over 20 years old, and is one of the most used build tools in the Java world. +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], used not only for the build itself but also by consumers. +This made Maven more than a tool; it became a whole ecosystem with many dependencies on the POM, especially the Maven +Central repository, other build tools, and IDEs. +But this stable schema comes at a price - the lack of flexibility. Review Comment: > Maven 4 does not seem to have improved in this regard. I agree on this, but I think that's not the direct, but only an indirect goal of Maven 4 as stated in the line below he quote: > Maven 4 will prepare for changes which are impossible nowadays, like a completely new build schema. As this is what's needed: Seperate build-pom from consumer one. So maven can do what ever it wants do to without breaking the ecosystem. May I ask how you would phrase the introduction of the article to point out the "same POM-problem? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
