[
https://jira.codehaus.org/browse/MASSEMBLY-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358651#comment-358651
]
Michael Osipov commented on MASSEMBLY-737:
------------------------------------------
Kristian, is that an easy fix?
> Generated WAR file does not contain the same default manifest entries as
> created by the Maven WAR Plugin
> --------------------------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-737
> URL: https://jira.codehaus.org/browse/MASSEMBLY-737
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Components: manifest, maven-archiver
> Affects Versions: 2.5.2
> Reporter: Michael Osipov
> Fix For: 2.5.3
>
> Attachments: massembly-737.zip
>
>
> I am repackaging a WAR file with some files exchanged. The original fiel
> contains following manifest entries:
> {noformat}
> Manifest-Version: 1.0
> Built-By: osipovmi
> Build-Jdk: 1.7.0_55
> Created-By: Apache Maven 3.2.2
> Archiver-Version: Plexus Archiver
> {noformat}
> The {{MANIFEST.MF}} generated by this plugin looks like:
> {noformat}
> Manifest-Version: 1.0
> Created-By: 24.55-b03 (Oracle Corporation)
> Archiver-Version: Plexus Archiver
> {noformat}
> while the descriptor looks very simple:
> {code}
> <assembly
>
> xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>
> xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.2
> http://maven.apache.org/xsd/assembly-1.1.2.xsd";>
> <id>deployable</id>
> <formats>
> <format>war</format>
> </formats>
> <includeBaseDirectory>false</includeBaseDirectory>
> <dependencySets>
> <dependencySet>
> <unpack>true</unpack>
> <useProjectArtifact>false</useProjectArtifact>
> </dependencySet>
> </dependencySets>
> </assembly>
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
