Releases
v3.0.2
Compare
Sorry, something went wrong.
No results found
Gmd-core
use CI-friendly parent version (${revision}) instead of a fixed parent version
openhtmltopdf [1.1.31 -> 1.1.37]
commonmark [0.26.0 -> 0.27.1]
junit [5.13.4 -> 6.0.2]
se.alipsa.matrix:matrix-bom [2.3.0 -> 2.4.0]
add compile-time JavaFX dependencies (javafx-controls, javafx-swing, javafx-web) for Java 21 compatibility
do not attach the fat jar assembly by default during package
Gmd-gradle-plugin
use CI-friendly parent version (${revision}) instead of a fixed parent version
upgrade Gradle wrapper [8.13 -> 9.3.1]
upgrade test baseline to JUnit BOM [5.13.4 -> 6.0.2]
add configurable javaFxVersion parameter
include platform-specific JavaFX runtime dependencies (javafx-base, javafx-graphics, javafx-controls, javafx-swing, javafx-web)
update plugin defaults to current stack (groovy 5.0.4, log4j 2.25.3, gmd 3.0.2)
upgrade Maven-side exec-maven-plugin [3.5.1 -> 3.6.3]
Gmd-maven-plugin
use CI-friendly parent version (${revision}) instead of a fixed parent version
add configurable dependency versions: groovyVersion, log4jVersion, gmdVersion, ivyVersion, javaFxVersion
resolve runtime dependencies dynamically with Maven Resolver and execute GmdProcessor in a forked JVM classpath
add platform-aware JavaFX dependency resolution (mac, mac-aarch64, linux, win)
add fallback mode to bundled dependencies when dynamic resolution is unavailable
upgrade plugin/dependency tooling (maven.version 3.9.11 -> 3.9.12, maven-plugin-annotations 3.15.1 -> 3.15.2, maven-plugin-testing-harness 3.3.0 -> 3.5.0)
You can’t perform that action at this time.