[SPARK-24715][Build] Override jline version as 2.14.3 in SBT

[viirya]

What changes were proposed in this pull request?

During SPARK-24418 (Upgrade Scala to 2.11.12 and 2.12.6), we upgrade jline version together. So, mvn works correctly. However, sbt brings old jline library and is hitting NoSuchMethodError in master branch, see #21495 (comment). This overrides jline version in SBT to make sbt build work.

How was this patch tested?

Manually test.

[viirya]

cc @dbtsai@dongjoon-hyun@HyukjinKwon

[HyukjinKwon]

Nice! Mind if I ask to show the diff between sbt dependency-tree vs mvn dependency:tree? Looks fine to me.

[viirya]

Hmm, it seems hard to compare the diff between sbt dependency-tree and mvn dependency:tree. Any suggestion?

[maropu]

If we don't override this, which jline version does sbt use? 2.12.1? (just a question...)

[viirya]

I've seen jline:jline:0.9.94 in sbt dependency-tree before this change.

[SparkQA]

Test build #92521 has finished for PR 21692 at commit 91ff758.

• This patch passes all tests.
• This patch merges cleanly.
• This patch adds no public classes.

[maropu]

Thanks, I feel it'd be better to put concrete version numbers in the description.

[viirya]

@maropu Thanks. Version number is in the description now.

[HyukjinKwon]

Merged to master.

[dbtsai]

@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?

[srowen]

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 -- most recent wins vs 'nearest' wins. Could be it.

[dongjoon-hyun]

Thank you all!

[viirya]

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 classes come from jline-2.14.3.jar.