!!! Configuration property names changed !!!
Since 0.1.0, all configuration property names start with mvnd. and the rest is camel case.
Please check the commented mvnd.properties file in the ZIP distribution or in the source tree.
Implemented enhancements:
- The daemon created by the client should survive if the client is interrupted using Ctrl+C #193
Closed issues:
- Performance regression after 668d4e4 #231
- The daemon is probably leaking memory #18
- Move mvnd logback config file into [MVND_HOME]/conf and use the standard name for the mvn specific config file #226
- Duration properties are not passed correctly to the daemon #225
- When the build does not produce any output, the elapsed time can be sluggish #224
- Use the
mvnd.prefix for all property names #221 - Exit code not propagated from the daemon to mvnd client #220
- pom.xml changes not honored (post 0.0.10 regression) #218
- Messages associated with projectId from the previous build in the terminal and daemon log #216
- Provide an automatic purge of daemon logs #196
- Document that mvnd may conflict with oh-my-zsh's alias for
mvn deploy#148 - ${my.property:-default} style defaults defined in logback.xml do not work #39
Merged pull requests:
- Upgrade to GraalVM 20.3.0 #235 (ppalaga)
- Output revision with -v/--version #233 (ppalaga)
- Avoid environment lookups and value conversions on hot paths #232 (ppalaga)
- Use more recent version of DeLaGuardo/setup-graalvm action #230 (gnodet)
- Make sure our CachingProjectBuilder is used, fixes #218 #228 (gnodet)
- Move mvnd logback config file into [MVND_HOME]/conf and use the stand… #227 (gnodet)
- Clean the names of properties, fixes #221 #223 (gnodet)
- Exit code not propagated from the daemon to mvnd client #222 (ppalaga)
- Messages associated with projectId from the previous build in the ter… #217 (ppalaga)
- Ignore INT and TSTP signals in the daemon #214 (gnodet)
- Automatic purge of daemon logs #213 (gnodet)