This was a small discrepancy to the output of vanilla Maven and made the output
hard to read, since the failure class name started right after the message without
any whitespace in between.
Changes:
* no source changes
* (build) expel all versions from child modules: they must be all top level depMgmt or pluginMgmt
* (build) Top POM contains GAVs while child modules GA+scope. This tremendously simplifies maintenance.
* (javadoc) fix Javadoc errors
Updates:
* use latest Maven 3.9.8-SNAPSHOT (TS locked version, controlled deploy by me)
* AssertJ 3.26.0
* Takari Smart Builder 0.6.6
* Sisu 0.9.0.M3
* maven wrapper 3.3.2 w/ scripts
This brings mvnd-1.x in "releasable" state (once Maven 3.9.8 is out).
Most of cumulative things dependabot reported, plus more.
Changes:
* use plugins from parent (instead to double-maintain them here as well)
* general cleanup, add property where there are 2+ uses for it
* update plugins not present in parent
* non-key dependencies (maven3, maven4, graalvm not touched) updates
Changes:
* parent POM 42
* unset release where needed (makes com.sun pkg unreachable)
* explicitly index as parent disables "implicit" AP
* remove redundtant stuff
* update dependabot to take care of workflow as well (as mvnd uses own)
* the logging framework is extracted into its own jar and moved in the mvn/lib/ directory
* the other daemon jars are moved into the mvn/lib/mvnd directory and not used by maven at all
This makes maven class loader almost identical to the stock maven classloader, but for the logging framework
