Prashant Sharma
authored
Actually false positive reported was due to mima generator not picking up the new jars in presence of old jars(theoretically this should not have happened.). So as a workaround, ran them both separately and just append them together. Author: Prashant Sharma <prashant@apache.org> Author: Prashant Sharma <prashant.s@imaginea.com> Closes #2285 from ScrapCodes/mima-fix and squashes the following commits: 093c76f [Prashant Sharma] Update mima 59012a8 [Prashant Sharma] Update mima 35b6c71 [Prashant Sharma] SPARK-3433 Fix for Mima false-positives with @DeveloperAPI and @Experimental annotations.
| Name | Last commit | Last update |
|---|---|---|
| .. | ||
| audit-release | ||
| create-release | ||
| README.md | ||
| check-license | ||
| github_jira_sync.py | ||
| lint-python | ||
| lint-scala | ||
| merge_spark_pr.py | ||
| mima | ||
| run-tests | ||
| run-tests-jenkins | ||
| scalastyle | ||