mbien commented on issue #5260: URL: https://github.com/apache/netbeans/issues/5260#issuecomment-1403701210
> Does mvnd fit in that use case? mvnd is just like maven but it has a warmed up daemon running in the background. Additionally the mvnd launcher is a native image which makes execution time of maven commands very fast while the "regular" hotspot JVM running the the background keeps as much state as possible without having to parse the pom again and again etc. Just point NetBeans to the mvnd installation instead of regular maven and most builds should "just work". mvnd runs many tasks in parallel, which is the main reason why some projects with more exotic plugins might fail. I have seen it happening before, but since maven and mvnd are a drop-in replacement its usually not a big deal - I simply switched back on a case by case basis. NB 17 will have some mvnd specific fixes since the maven output looks slightly different which confused the stacktrace linker and things like that. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
