You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "liupengcheng (JIRA)" <ji...@apache.org> on 2019/01/04 02:17:00 UTC
[jira] [Commented] (SPARK-26126) Should put scala-library deps into
root pom instead of spark-tags module
[ https://issues.apache.org/jira/browse/SPARK-26126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16733738#comment-16733738 ]
liupengcheng commented on SPARK-26126:
--------------------------------------
[~hyukjin.kwon] it's an issue, it's really doesn't matter, but it's just confusing.
> Should put scala-library deps into root pom instead of spark-tags module
> ------------------------------------------------------------------------
>
> Key: SPARK-26126
> URL: https://issues.apache.org/jira/browse/SPARK-26126
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 2.1.0, 2.3.0, 2.4.0
> Reporter: liupengcheng
> Priority: Minor
>
> When I do some backport in our custom spark, I notice some strange code from spark-tags module:
> {code:java}
> <dependencies>
> <dependency>
> <groupId>org.scala-lang</groupId>
> <artifactId>scala-library</artifactId>
> <version>${scala.version}</version>
> </dependency>
> </dependencies>
> {code}
> As i known, should spark-tags only contains some annotation related classes or deps?
> should we put the scala-library deps to root pom?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org