Bug 1094181

Description of problem:

I tried to deploy SOAP quickstart from JBoss Fuse 6.1 using maven build, and the deployment phase failed when processing the archive contents.

Version-Release number of selected component (if applicable):
* FSW/S-RAMP 6.0.0
* Fuse 6.1

How reproducible:
* 100%

Steps to Reproduce:
1. Start FSW/S-RAMP
2. cd to Fuse (not FSW) quickstarts folder, and configure pom.xml to deploy to local S-RAMP repository:
* enable s-ramp wagon in build extensions
* configure S-RAMP repository in distributionManagement
* see: http://documentation-devel.engineering.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Fuse_Service_Works/6/html-single/Development_Guide_Volume_3_Governance/index.html#Deploying_to_S-RAMP
3. execute mvn clean deploy

Actual results:

[INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @ camel-webservice ---
Uploading: sramp://localhost:8080/s-ramp-server/?artifactType=JavaArchive/com/mycompany/camel-webservice/1.0.1/camel-webservice-1.0.1.jar
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/sbunciak/.m2/repository/org/slf4j/slf4j-log4j12/1.7.2-redhat-1/slf4j-log4j12-1.7.2-redhat-1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/sbunciak/.m2/repository/org/slf4j/slf4j-nop/1.7.2-redhat-1/slf4j-nop-1.7.2-redhat-1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
[INFO] Uploading s-ramp artifact: com/mycompany/camel-webservice/1.0.1/camel-webservice-1.0.1.jar
Uploading: sramp://localhost:8080/s-ramp-server/?artifactType=JavaArchive/com/mycompany/camel-webservice/1.0.1/camel-webservice-1.0.1.pom
[INFO] Uploading s-ramp artifact: com/mycompany/camel-webservice/1.0.1/camel-webservice-1.0.1.pom
[INFO] Uploading s-ramp artifact: com/mycompany/camel-webservice/1.0.1/camel-webservice-1.0.1.pom.sha1
[INFO] Storing hash value as s-ramp property: camel-webservice-1.0.1.pom.sha1
[INFO] Uploading s-ramp artifact: com/mycompany/camel-webservice/1.0.1/camel-webservice-1.0.1.pom.md5
[INFO] Storing hash value as s-ramp property: camel-webservice-1.0.1.pom.md5
Uploaded: sramp://localhost:8080/s-ramp-server/?artifactType=JavaArchive/com/mycompany/camel-webservice/1.0.1/camel-webservice-1.0.1.pom (0 B at 0.0 KB/sec)
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 14.787s
[INFO] Finished at: Sun May 04 15:27:16 CEST 2014
[INFO] Final Memory: 52M/446M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy (default-deploy) on project camel-webservice: Failed to deploy artifacts: Could not transfer artifact com.mycompany:camel-webservice:jar:1.0.1 from/to local-sramp-repo (sramp://localhost:8080/s-ramp-server/?artifactType=JavaArchive): java.io.IOException: Failed to create directory: /tmp/j2sramp3872576220373030920.work/META-INF -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

Expected results:


Additional info:

* This is caused bu a bug in ArchiveUtils class, however until now, the users were not affected