-
Notifications
You must be signed in to change notification settings - Fork 135
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
Exclude Spark UnusedStubClass from class uniqueness #2390
Conversation
Spark UnusedStubClass exists for mechanical reasons and is as described, never used. With this PR it is skipped, like module-infos. Potential badness: It's possible that this change would block excavators on certain projects by changing the set of duplicated classes. I think it's likely that this would simply require approval from a human, depending on how the excavator was written.
Generate changelog in
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks reasonable to me. At the limit this would become a large central list, but if it grows we can consider moving to an extension model for archetype-specific values
Released 4.169.0 |
###### _excavator_ is a bot for automating changes across repositories. Changes produced by the roomba/latest-baseline-oss check. # Release Notes ## 4.168.0 | Type | Description | Link | | ---- | ----------- | ---- | | Fix | Roll back nullaway+checkerframework for jdk15 support | palantir/gradle-baseline#2389 | ## 4.169.0 | Type | Description | Link | | ---- | ----------- | ---- | | Improvement | Exclude Spark UnusedStubClass from class uniqueness | palantir/gradle-baseline#2390 | To enable or disable this check, please contact the maintainers of Excavator.
Spark UnusedStubClass exists for mechanical reasons and is as described, never used. With this PR it is skipped, like module-infos.
Potential badness: It's possible that this change would block excavators on certain projects by changing the set of duplicated classes. I think it's likely that this would simply require approval from a human, depending on how the excavator was written.