HomeOfTheWizard commented on issue #496: URL: https://github.com/apache/maven-mvnd/issues/496#issuecomment-2270771295
@wallentx I think it is possible this cache extension with mvnd ``` mvnd.coreExtensions: internal option to specify the list of maven extension to register For a full list of available properties please see [/dist/src/main/distro/conf/mvnd.properties](https://github.com/apache/maven-mvnd/blob/master/dist/src/main/distro/conf/mvnd.properties). ``` But it does not address all the requirements listed in the discussion here. If I understood well from the documentation it is for incremental builds, meaning it helps to skip parts of the project that is already executed. For instance, I suppose it will not be used for the below specifities of mvnd: caching the class loaders of the plugins executed by the previous builds, or the byte code generated by the JIT in the. From the README: ``` This architecture brings the following advantages: The JVM for running the actual builds does not need to get started anew for each build. The class loaders holding classes of Maven plugins are cached over multiple builds. The plugin jars are thus read and parsed just once. SNAPSHOT versions of Maven plugins are not cached. The native code produced by the Just-In-Time (JIT) compiler inside the JVM is kept too. Compared to stock Maven, less time is spent by the JIT compilation. During the repeated builds the JIT-optimized code is available immediately. This applies not only to the code coming from Maven plugins and Maven Core, but also to all code coming from the JDK itself. ``` IMHO the way is to be able to use a remote centralized long running daemon from multiple mvnd clients, or externalize the cache of the daemon so it can be shared but that might be a bit more complex if the daemons sharing the same cache runs different plugins/tasks. -- 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
