[
http://jira.codehaus.org/browse/MASSEMBLY-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206490#action_206490
]
Mike Key commented on MASSEMBLY-463:
------------------------------------
It would appear this issue can likely be closed or reduced to a request rather
than an issue. The actual issue appears to be a network bottleneck and
synchronization one between maven and artifactory 2.0.7 while running with its
default jetty as the server. The actual error appears to be a broken pipe.
However the broken pipe occurs when the following command tries to upload any
assembly twice (2 times) to artifactory. This can be seen with the dual log
messages:
[INFO] [install:install {execution: default-install}]
[INFO] Installing
/opt/scm/.hudson/jobs/live-ensure-trunk/workspace/trunk/tools/target/live-ensure-tools-1.0.0-SNAPSHOT.jar
to
/opt/scm/.m2/repository/com/liveensure/tools/live-ensure-tools/1.0.0-SNAPSHOT/live-ensure-tools-1.0.0-SNAPSHOT.jar
[INFO] Installing
/opt/scm/.hudson/jobs/live-ensure-trunk/workspace/trunk/tools/target/live-ensure-tools-1.0.0-SNAPSHOT-scripts.zip
to
/opt/scm/.m2/repository/com/liveensure/tools/live-ensure-tools/1.0.0-SNAPSHOT/live-ensure-tools-1.0.0-SNAPSHOT-scripts.zip
[INFO] Installing
/opt/scm/.hudson/jobs/live-ensure-trunk/workspace/trunk/tools/target/live-ensure-tools-1.0.0-SNAPSHOT-scripts.zip
to
/opt/scm/.m2/repository/com/liveensure/tools/live-ensure-tools/1.0.0-SNAPSHOT/live-ensure-tools-1.0.0-SNAPSHOT-scripts.zip
[INFO] [deploy:deploy {execution: default-deploy}]
[INFO] Retrieving previous build number from mastlabs-snapshots
Uploading:
http://myhost/artifactory/mast-snapshot-repo/com/tools/tools/1.0.0-SNAPSHOT/mytools-tools-1.0.0-20100111.192856-278.jar
1K uploaded (mytools-1.0.0-20100111.192856-278.jar)
[INFO] Uploading project information for mytools-tools 1.0.0-20100111.192856-278
[INFO] Retrieving previous metadata from snapshots
[INFO] Uploading repository metadata for: 'snapshot
com.tools:mytools-tools:1.0.0-SNAPSHOT'
[INFO] Retrieving previous metadata from snapshots
[INFO] Uploading repository metadata for: 'artifact com.tools:live-ensure-tools'
[INFO] Retrieving previous build number from snapshots
Uploading:
http://ml02:8081/artifactory/snapshot-repo/com/tools/mytools-tools/1.0.0-SNAPSHOT/mytools-tools-1.0.0-20100111.192856-278-scripts.zip
44K uploaded (mytools-tools-1.0.0-20100111.192856-278-scripts.zip)
[INFO] Retrieving previous build number from snapshots
Uploading:
http://ml02:8081/artifactory/snapshot-repo/com/tools/mytools-tools/1.0.0-SNAPSHOT/mytools-tools-1.0.0-20100111.192856-278-scripts.zip
44K uploaded (mytools-tools-1.0.0-20100111.192856-278-scripts.zip)
[HUDSON] Archiving
/opt/scm/.hudson/jobs/live-ensure-trunk/workspace/trunk/tools/pom.xml to
/opt/scm/.hudson/jobs/live-ensure-trunk/modules/com.liveensure.tools$mytools-tools/builds/2010-01-11_12-28-49/archive/com.tools/tools/1.0.0-SNAPSHOT/pom.xml
> Assembly fails Problem creating war: JAR entry not found
> --------------------------------------------------------
>
> Key: MASSEMBLY-463
> URL: http://jira.codehaus.org/browse/MASSEMBLY-463
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-5
> Environment: CentOS or Debian, Java 6.0-16
> Reporter: Mike Key
> Attachments: distribution.xml
>
>
> When doing a build through hudson on either a Debian or CentOS machine (the
> only two I've tested) the assembly plugin fails with a message like this:
> Failed to create assembly: Error creating assembly archive distribution:
> Problem creating war: JAR entry [[filename.random]] not found in
> /path/to/war/extracted/from
> In this depending on what maven options are used, various different files
> show up as not found in the war being extracted from to create the assembly.
> However, the file ALWAYS exists.
> This issue ONLY occurs when the build goals include the 'deploy' goal. In
> other words, if I run 'mvn clean package' or mvn clean install' the issue
> does not exist, but if I run 'mvn clean package deploy' or 'mvn clean install
> deploy' the assembly fails.
> Note that USUALLY, running another build seems to clear up the issue, but not
> always. But the issue does break out CI process.
> Attached is the assembly itself. I was never able to associate any change to
> this assembly contributing to the start of this issue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
