Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While there are significant usages of
gmavenplus-plugin
that remain (e.g.pipeline-model-definition
), there are no significant plugins that build with Maven and have Groovy tests. At least runningfind . -type d -name groovy | grep src.test.groovy
in my local checkout directory with the top 250 plugins turned up no results. Better to delete this unused configuration. To test this change I successfully ranmvn clean verify
inpipeline-model-definition-plugin
(the only significant plugin still usinggmavenplus-plugin
) with these changes.