Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
2.0.0
-
None
Description
There are several instances where we are still using org.apache.commons.lang classes instead of org.apache.commons.lang3. Only the latter is a direct dependency.
That's easy enough to fix. I think it might be important for 2.0.0 even at this late hour, because in addition, Commons Lang's NotImplementedException is being used where I believe the JDK's standard UnsupportedOperationException is appropriate. Since these exceptions may conceivably propagate and be handled by user code they sorta become part of an API.
Attachments
Issue Links
- is related to
-
SPARK-47039 Add a checkstyle rule to ban `commons-lang` in Java code
- Resolved
- links to