Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ignore additional classpath on usecase when using the plugin #131

Merged
merged 2 commits into from
Dec 4, 2024

Conversation

harrisric
Copy link
Contributor

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.

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.
@RadikalJin RadikalJin merged commit 7a38717 into main Dec 4, 2024
2 checks passed
@RadikalJin RadikalJin deleted the plugin-ignore-additional-classpath branch December 4, 2024 12:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants