Releases: gradlex-org/maven-plugin-development
v1.0.3
v1.0.2
v1.0.1 - Kotlin DSL hot fix
- [Fixed] #290 Configuring the plugin is broken in Kotlin DSL.
v1.0 - Move to GradleX
This release marks the move of this plugin to the GradleX project.
Consequently, this is a breaking release with features being dropped, plugin ID and code coordinate changes, and the implementation language changing from Kotlin to Java.
The minimal required Gradle version has been increased to 7.5.
- [Fixed] #57 Remove javaClassesDir from GenerateMavenPluginDescriptorTask.
- [Fixed] #210 Drop feature: Mojo source set.
It's no longer possible to define a dedicated source set for defining the mojo. Use a dedicated project instead. - [Fixed] #212 Drop feature: Finding mojos in project dependencies.
The plugin no longer searches for mojo implementations in dependent projects since this is not the way of modelling aggregation of build results in Gradle. Users who rely on this use case should instead apply this plugin to all projects with mojo implementations, set up a variant that exposes the descriptor, and then merge all exposed descriptor variants in an aggregator project. - [Fixed] 209 Drop feature: Mojo DSL.
This feature was dropped without replacement. Annotate mojos using annotations defined inorg.apache.maven.plugin-tools:maven-plugin-annotations
instead of declaring them in your build script. - [Fixed] 278 Remove deprecated code.
In particular this thegenerateHelpMojo
property was removed. Users should configurehelpMojoPackage
with the desired target package for the generated help mojo. - [Fixed] 8 Support configuration cache.
- [Fixed] 38 Don't use Property for lazy types.
Instead of declaring fields of typeProperty<FileCollection>
theGenerateMavenPluginDescriptorTask
not declares fields of typeConfigurableFileCollection
, which is more idiomatic. - [Fixed] 78 Migration to Java.
- [Fixed] 203 Migration to GradleX namespace.
- [Fixed] 283 Fix deprecation issued for accessing other projects.
Gradle 8 compatibility
Java 17 support
This release only contains a single change (#89) which restores Java 17 compatibility. Thank you @dariuszkuc for contributing this fix.
Mojo class hierarchy support
Bug fixes
- Descriptor generation is up to date although mojo dependency changed (#13)
@Parameter
in abstract classes in other modules are ignored (#73)
Breaking changes
- The
mojo
configuration was removed without replacement. The plugin now searches the compile classpath instead. - Property
mojoDependencies
dropped fromGenerateMavenPluginDescriptorTask
without replacement.
Full Changelog: 0.3.1...0.4.0
Minor fixes and improvements
Fixed UP-TO-DATE checking
This release fixes UP-TO-DATE checking which previously did not work.
This come however at the cost of an incompatible change so users have to modify their builds in order to continue using the plugin.
Note: This release includes a change in behavior of the HelpMojo generation.
Before 0.3.0 generation of a HelpMojo could be turned on by setting generateHelpMojo
to true
.
Starting with 0.3.0 generateHelpMojo
is deprecated and replaced by helpMojoPackage
.
Users now need to define the package of the HelpMojo.
This fixes problems with up-to-date checking (see #16).
Bug fixes
- Task descriptions for help and descriptor task are swapped (#34)
- Help mojo task is never up to date because descriptor tasks modifies outputs (#16)
Deprecations
- The
generateHelpMojo
setting has been deprecated in favor ofhelpMojoPackage
Breaking changes
- Class
de.benediktritter.maven.plugin.development.task.HelpGeneratorAccessor
has been removed
Better documentation
I'm happy to announce the third release of maven-plugin-development
! 🎉 Most of the work in this release went into the documentation which is no based on Asciidoctor and can be viewed on here.
New Features
- Tasks provide proper descriptions (#22)