Github user viirya commented on the issue:
https://github.com/apache/spark/pull/21692
@maropu Thanks. Version number is in the description now.
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For a
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/21692
Merged to master.
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews
Github user dbtsai commented on the issue:
https://github.com/apache/spark/pull/21692
@viirya thanks for this PR. I thought SBT always uses pom for dependencies,
and I wonder why there is a discrepancy so we need to manually override it?
---
-
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/21692
I haven't looked into this particular issue thoroughly, but, I'm aware that
SBT and Maven don't actually resolve dependencies in quite the same way. I
think the resolve conflicts with different rules
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/21692
Thank you all!
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/21692
Thanks @srowen for explanation. As I can tell, `-verbose:class` shows jline
classes come from `jline-2.12.jar`, though `sbt dependency-tree` shows
`jline:jline:0.9.94`. After this overriding, jline c