Remove mrm-maven-plugin
#828
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.
I cannot see a reason to continue using
mrm-maven-plugin. Based on https://www.mojohaus.org/mrm/mrm-maven-plugin/examples/invoker-tests.html it seems the reason for using it was originallybut I just ran
mvn clean verifyand my local~/.m2repository did not seem to get polluted, so I don't think this is a concern anymore now that we are configuringmaven-invoker-pluginwithlocalRepositoryPath.For what it's worth, I asked Maven developer Tamás Cservenák to audit
maven-hpi-plugina few months back, and here is what he had to say: