[SPARK-11732] Removes some MiMa false positives#9697
Conversation
|
Test build #45875 has finished for PR 9697 at commit
|
There was a problem hiding this comment.
You also added protected here though; I'm not sure that's safe to exclude from checks.
The point is that some previous excludes are now caught by the new isPrivate check and ignored?
There was a problem hiding this comment.
After checking the scala specs, the protected modifier only affects methods, not classes. I am removing it.
There was a problem hiding this comment.
About your previous question, yes, isPrivate catches some classes that we did not catch previously (because we were checking for package-private classes, not private classes).
|
@srowen sorry the delay. comment addressed |
|
Test build #46006 has finished for PR 9697 at commit
|
|
LGTM @pwendell as I can't see why MiMa would need to look at private classes of any type. |
|
Yep, this LGTM |
|
Merged to master/1.6 |
This adds an extra filter for private or protected classes. We only filter for package private right now. Author: Timothy Hunter <timhunter@databricks.com> Closes #9697 from thunterdb/spark-11732. (cherry picked from commit fa603e0) Signed-off-by: Sean Owen <sowen@cloudera.com>
|
Thank you @srowen |
This adds an extra filter for private or protected classes. We only filter for package private right now.