Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/1813#discussion_r16493141
--- Diff: pom.xml ---
@@ -1017,6 +1018,21 @@
<profiles>
+ <!--
+ This profile is enabled automatically by the sbt built. It changes
the scope for the guava
+ dependency, since we don't shade it in the artifacts generated by
the sbt build.
+ -->
+ <profile>
+ <id>sbt</id>
+ <dependencies>
+ <dependency>
+ <groupId>com.google.guava</groupId>
+ <artifactId>guava</artifactId>
+ <scope>compile</scope>
--- End diff --
sorry - I see - the issue is that elsewhere this is not in compile scope.
However, why not just have it be compile scope by default in the root pom? Is
the issue that we need to make sure it does not exist at compile scope in our
published root pom?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
