gnodet commented on code in PR #598: URL: https://github.com/apache/maven-site/pull/598#discussion_r1894641014
########## content/markdown/whatsnewinmaven4.md: ########## @@ -390,6 +390,15 @@ improvements, e.g., a Java native HTTP-Client - thanks to raising the Java versi Another major difference compared to Maven 3 is that in the new major version, the resolver is hidden behind the new Maven API and is no longer used directly by plugins. +### Maven Shell + +When you run any `mvn` command, the full chain of booting Java, Maven, load config, do the work, tear down and exit the +process is done - **every single time**. +To improve performance and reduce build time, you can use the [Maven Daemon][29] (`mvnd`), which manages a pool of N +resident Maven processes. +With Maven 4 you can also use the brightly polished "Maven Shell" (`mvnsh`), which will keep exactly one resident Maven +process as long as the shell is opened. Review Comment: ``` ### Maven Shell Each time you run an `mvn` command, the entire process chain is executed: booting Java, starting Maven, loading the configuration, performing the task, tearing down, and exiting — **every single time**. To improve performance and reduce build times, you can use the [Maven Daemon][29] (`mvnd`), which manages a pool of resident Maven processes. With Maven 4, you can also take advantage of the newly defined "Maven Shell" (`mvnsh`), which keeps a single Maven process running for as long as the shell remains open. ``` Minor improvements to this section. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
