You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Marcelo Vanzin (JIRA)" <ji...@apache.org> on 2016/03/11 19:29:01 UTC
[jira] [Resolved] (SPARK-13780) SQL "incremental" build in maven is
broken
[ https://issues.apache.org/jira/browse/SPARK-13780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcelo Vanzin resolved SPARK-13780.
------------------------------------
Resolution: Fixed
Assignee: Marcelo Vanzin
Fix Version/s: 2.0.0
> SQL "incremental" build in maven is broken
> ------------------------------------------
>
> Key: SPARK-13780
> URL: https://issues.apache.org/jira/browse/SPARK-13780
> Project: Spark
> Issue Type: Bug
> Components: Build, SQL
> Reporter: Marcelo Vanzin
> Assignee: Marcelo Vanzin
> Priority: Minor
> Fix For: 2.0.0
>
>
> If you build Spark, and later try to build just the SQL module like this:
> {code}
> mvn ... -pl :spark-sql_2.11
> {code}
> You end up with a nasty error:
> {noformat}
> [error] uncaught exception during compilation: scala.reflect.internal.Types$TypeError
> scala.reflect.internal.Types$TypeError: bad symbolic reference. A signature in WebUI.class refers to term servlet
> in value org.jetty which is not available.
> It may be completely missing from the current classpath, or the version on
> {noformat}
> This is because of bad interaction between shading, Scala's signature field, and internal APIs exposing shaded classes.
> The fix is simple, we just need to add an explicit dependency on the jetty artifacts to the sql module.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org