Ignore additional classpath on usecase when using the plugin #131
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.
It is not appropriate for the plugin to assume that an arbitrary classpath will be present (particularly if used in CI-type pipelines). In order for the before refactor classes to compile the classpath will already need to include the class path. If the 'after' classpath needs to be different either the project pom can be amended upfront or else the plugin can be declared with additional dependencies.