[ https://issues.apache.org/jira/browse/SPARK-14797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryan Blue updated SPARK-14797: ------------------------------ Comment: was deleted (was: [~joshrosen], I can no longer build using maven after this commit. I'm getting an error from the new enforcer rules: {code} [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-versions) @ spark-parent_2.11 --- [WARNING] Rule 0: org.apache.maven.plugins.enforcer.BannedDependencies failed with message: Found Banned Dependency: org.scala-lang.modules:scala-xml_2.11:jar:1.0.2 Found Banned Dependency: org.scalatest:scalatest_2.11:jar:2.2.6 Use 'mvn dependency:tree' to locate the source of the banned dependencies. {code} The version set in the root POM for scalatest_2.11 is 2.2.6, so I think that there's a problem with the rule.) > Spark SQL should not hardcode dependency on spark-sketch_2.11 > ------------------------------------------------------------- > > Key: SPARK-14797 > URL: https://issues.apache.org/jira/browse/SPARK-14797 > Project: Spark > Issue Type: Bug > Components: Build > Reporter: Josh Rosen > Assignee: Josh Rosen > Fix For: 2.0.0 > > > Spark SQL's POM hardcodes a dependency on spark-sketch_2.11, but it > substitute scala.binary.version instead of hardcoding 2.11. We should fix > this and add a Maven Enforcer rule to prevent this from ever happening again. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org