- [Fixed] #295 Build no longer fails when Mojo project depends on a Kotlin library project. Thanks to @DreierF.
- [Fixed] #290 Configuring the plugin is broken in Kotlin DSL.
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 in
org.apache.maven.plugin-tools:maven-plugin-annotations
instead of declaring them in your build script. - [Fixed] 278 Remove deprecated code.
In particular this the
generateHelpMojo
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 type
Property<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.
- [Fixed] #166 Fix deprecation warnings. Thanks to Zongle Wang.
- [Fixed] #94 Make plugin compatible with Gradle 8.x
- [Fixed] #89 Make plugin compatible with Java 17
- [Fixed] #13 Descriptor generation is up to date although mojo dependency changed
- [Fixed] #73
@Parameter
in abstract classes in other modules are ignored
- The
mojo
configuration was removed without replacement. The plugin now searches the compile classpath instead. - Property
mojoDependencies
dropped fromGenerateMavenPluginDescriptorTask
without replacement.
- [New] #7 Build cache support
- [New] #26 Plugin jar contains LICENSE file
- [New] #47 Additional project metadata added to published plugin POMs
- [New] #35 More idiomatic task dependency modelling
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).
- [Fixed] #34 Task descriptions for help and descriptor task are swapped
- [Fixed] #16 Help mojo task is never up to date because descriptor tasks modifies outputs
- The
generateHelpMojo
setting has been deprecated in favor ofhelpMojoPackage
- Class
de.benediktritter.maven.plugin.development.task.HelpGeneratorAccessor
has been removed
- [New] #22 Tasks provide proper descriptions
- [Fixed] #19 Build fails when
java
plugin is not applied explicitly - [Fixed] #23 Typing of
parameters
API is incorrect
- [New] #4 Add DSL for declaring mojos in the build script
- [New] #12 Provide way to configure plugin dependencies
- [New] #11 Define dedicated configuration for projects providing mojos
- [New] #3 Add support for mojos from other projects
- [Fixed] #9 Force version upgrade of qdox
- Package
de.benediktritter.maven.plugin.development.model
has been removed.
Initial release