pom.xml: make Maven integration plugin optional #231
Merged
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.
maven-plugin has been added as a dependency with 30ca891 along with jenkins-war 2.3 and jenkins-core 2.3 and I guess it was no more bundled in Jenkins as a result.
The only usage is in hudson.plugins.im.bot.HealthCommandTest, otherwhise instant messaging does not depend on the plugin, it merely supports it.
Make the Maven plugin optional, this allows administrators to remove the plugin when it is otherwise not used.
Note: given the Maven plugin is only needed for testing the integration, my guess is that it should also be marked with
<scope>test</scope>
?Testing done
Submitter checklist