Remove deprecated features from plugin-maven, and let plugin-gradle zombie-along #630
+49
−316
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.
At this point, we can't remove anymore deprecated code from
lib
orlib-extra
unless we also remove the deprecated user-facing parts ofplugin-maven
andplugin-gradle
.This PR removes all deprecated functionality from
plugin-maven
.I'd like to delay breaking
plugin-gradle
for another week or two. So, I moved all the deprecated parts oflib
andlib-extra
over toplugin-gradle
in a.libdeprecated
package. The code will live there just until the very-soon breaking change toplugin-gradle
, at which point we'll be free of it forever.So after this PR,
lib
has no deprecated code, andplugin-maven
has no deprecated code.plugin-gradle
has a lot, but it can all be removed in an upcoming cleanup.