Github user nchammas commented on a diff in the pull request:
https://github.com/apache/spark/pull/12004#discussion_r57613179
--- Diff: cloud/pom.xml ---
@@ -0,0 +1,141 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+ ~ Licensed to the Apache Software Foundation (ASF) under one or more
+ ~ contributor license agreements. See the NOTICE file distributed with
+ ~ this work for additional information regarding copyright ownership.
+ ~ The ASF licenses this file to You under the Apache License, Version 2.0
+ ~ (the "License"); you may not use this file except in compliance with
+ ~ the License. You may obtain a copy of the License at
+ ~
+ ~ http://www.apache.org/licenses/LICENSE-2.0
+ ~
+ ~ Unless required by applicable law or agreed to in writing, software
+ ~ distributed under the License is distributed on an "AS IS" BASIS,
+ ~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied.
+ ~ See the License for the specific language governing permissions and
+ ~ limitations under the License.
+ -->
+<project xmlns="http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
+ <modelVersion>4.0.0</modelVersion>
+ <parent>
+ <groupId>org.apache.spark</groupId>
+ <artifactId>spark-parent_2.11</artifactId>
+ <version>2.0.0-SNAPSHOT</version>
+ <relativePath>../pom.xml</relativePath>
+ </parent>
+
+ <artifactId>spark-cloud_2.11</artifactId>
+ <packaging>jar</packaging>
+ <name>Spark Project cloud integration</name>
+ <description>Contains support for cloud infrastructures, including the
Hadoop JARs and
+ transitive dependencies needed to interact with the infrastructures.
+ When included in the spark-assembly JAR, the hadoop artifacts are
included, but not
+ any of the 3rd party libraries needed, such as those from Amazon (for
AWS) and Microsoft (Azure).
+ These will need to be explicitly added to the classpath of any
application interacting
+ with the services.
+
+ Any project which explicitly depends upon the spark-cloud artifact
will get the dependencies;
+ the exact versions of which will depend upon the hadoop version Spark
was compiled against.
+
+ Hadoop 2.5 and earlier: jets3t.
+ Hadoop 2.6: hadoop-aws and aws-java-sdk JARs
+ Hadoop 2.7+: hadoop-aws, aws-java-sdk-s3, hadoop-azure and
azure-storage JARs
+
+ WARNING: the signatures of methods in aws-java-sdk/aws-java-sdk-s3 can
change between versions:
+ use the same version against which Hadoop was compiled.
+ </description>
+ <properties>
+ <sbt.project.name>cloud</sbt.project.name>
+ </properties>
+
+ <dependencies>
+ <dependency>
+ <groupId>org.apache.spark</groupId>
+ <artifactId>spark-core_${scala.binary.version}</artifactId>
+ <version>${project.version}</version>
+ </dependency>
+ <dependency>
+ <groupId>org.apache.spark</groupId>
+ <artifactId>spark-core_${scala.binary.version}</artifactId>
+ <version>${project.version}</version>
+ <type>test-jar</type>
+ <scope>test</scope>
+ </dependency>
+ <dependency>
+ <groupId>org.apache.spark</groupId>
+ <artifactId>spark-test-tags_${scala.binary.version}</artifactId>
+ </dependency>
+ <dependency>
+ <groupId>net.java.dev.jets3t</groupId>
+ <artifactId>jets3t</artifactId>
+ </dependency>
+
+ <!-- Explicit listing of transitive deps that are shaded. Otherwise,
odd compiler crashes. -->
+ <dependency>
+ <groupId>com.google.guava</groupId>
+ <artifactId>guava</artifactId>
+ </dependency>
+ <!-- End of shaded deps. -->
+ </dependencies>
+ <build>
+
<outputDirectory>target/scala-${scala.binary.version}/classes</outputDirectory>
+
<testOutputDirectory>target/scala-${scala.binary.version}/test-classes</testOutputDirectory>
+ </build>
+
+ <profiles>
+
+ <!--
+ This profile is enabled automatically by the sbt built. It changes
the scope for the guava
--- End diff --
Typo: By the sbt build.
---
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]
