[
http://jira.codehaus.org/browse/MASSEMBLY-463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208615#action_208615
]
Thomas Francart commented on MASSEMBLY-463:
-------------------------------------------
We are having the same error here.
However the issue does not occur in a 'deploy' goal; we don't have interaction
with an artifactory repository. But we do run 2 goals in a single maven command
: 'mvn package assembly:assembly'.
The error is systematic, although the file name that is not found changes. The
file is always here.
We are using the default 'jar-with-dependency' assembly configuration.
And the assembly plugin is called directly from inside our pom. Meaning when we
do 'mvn package assembly:assembly', the assembly is called 2 times.
See the attached pom.xml and detailed massembly-463.log files. In
massembly-463.log I have extracted the logs from the 2 times when the project
is built : the first one is OK, the second one fails.
> 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
