SPARK-7481: artifact is spark-hadoop-cloud while project is hadoop-cl…

…oud. Added an extra callout to the docs "without some form of consistency layer, Amazon S3 cannot

be safely used as the direct destination of work with the normal rename-based committer"

That holds for all Spark-in-EC deployments; EMR has a consistency option, as do/will others; different committers can work reliably.

Change-Id: Ibbf8b1b9de10b5bb83b647cc663ceb970f70ff2d
Testing: SBT and maven, with & without the hadoop-2.7 option.

assembly/pom.xml

@@ -235,7 +235,7 @@
       <dependencies>
         <dependency>
           <groupId>org.apache.spark</groupId>
-          <artifactId>hadoop-cloud_${scala.binary.version}</artifactId>
+          <artifactId>spark-hadoop-cloud_${scala.binary.version}</artifactId>
           <version>${project.version}</version>
         </dependency>
       </dependencies>

docs/cloud-integration.md

@@ -64,6 +64,9 @@ For these reasons, it is not always safe to use an object store as a direct dest
 an intermediate store in a chain of queries. Consult the documentation of the object store and its
 connector to determine which uses are considered safe.
 
+In particular: *without some form of consistency layer, Amazon S3 cannot
+be safely used as the direct destination of work with the normal rename-based committer.*
+
 ### Installation
 
 With the relevant libraries on the classpath and Spark configured with valid credentials,

hadoop-cloud/pom.xml

@@ -26,7 +26,7 @@
     <relativePath>../pom.xml</relativePath>
   </parent>
 
-  <artifactId>hadoop-cloud_2.11</artifactId>
+  <artifactId>spark-hadoop-cloud_2.11</artifactId>
   <packaging>jar</packaging>
   <name>Spark Project Cloud Integration</name>
   <description>