[jira] [Closed] (MASSEMBLY-463) Assembly fails Problem creating war: JAR entry not found

["Michael Osipov (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MASSEMBLY-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MASSEMBLY-463.
------------------------------------
    Resolution: Incomplete

Project does not build with supplied POM:

{noformat}
[INFO] Scanning for projects...
Downloading: https://repo.maven.apache.org/maven2/com/mondeca/maven-config/1.0/maven-config-1.0.pom
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[WARNING] 'version' contains an expression but should be a constant. @ line 13, column 12
[FATAL] Non-resolvable parent POM for com.mondeca.itm:export:${itm-version}: Could not find artifact com.mondeca:maven-config:pom:1.0 in central (https://repo.maven.apache.org/maven2) and 'parent.relativePath' points at wrong local POM @ line 7, column 11
 @
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR]   The project com.mondeca.itm:export:${itm-version} (C:\Users\mosipov\Downloads\pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM for com.mondeca.itm:export:${itm-version}: Could not find artifact com.mondeca:maven-config:pom:1.0 in central (https://repo.maven.apache.org/maven2) and 'parent.relativePath' points at wrong local POM @ line 7, column 11 -> [Help 2]
[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/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
{noformat}

and supplied assembly descriptor is useless without a proper POM.

> Assembly fails Problem creating war: JAR entry not found
> --------------------------------------------------------
>
>                 Key: MASSEMBLY-463
>                 URL: https://issues.apache.org/jira/browse/MASSEMBLY-463
>             Project: Maven 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, massembly-463.log, pom.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 was sent by Atlassian JIRA
(v6.3.4#6332)