apache / apache/maven-assembly-plugin

[MASSEMBLY-737] Generated WAR file does not contain the same default manifest entries as created by the Maven WAR Plugin

Open
#950 13 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Java
Stars
110
Forks
75
Avg merge
12h 54m
Merged PRs (30d)
10

Description

**[Michael Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)** opened **[MASSEMBLY-737](https://issues.apache.org/jira/browse/MASSEMBLY-737?redirect=false)** and commented

I am repackaging a WAR file with some files exchanged. The original file contains following manifest entries:

```
Manifest-Version: 1.0
Built-By: osipovmi
Build-Jdk: 1.7.0_55
Created-By: Apache Maven 3.2.2
Archiver-Version: Plexus Archiver
```

The `MANIFEST.MF` generated by this plugin looks like:

```
Manifest-Version: 1.0
Created-By: 24.55-b03 (Oracle Corporation)
Archiver-Version: Plexus Archiver
```

while the descriptor looks very simple:

```

deployable

war

false


true
false

```

---

**Affects:** 2.5.2

**Attachments:**
- [massembly-737.zip](https://issues.apache.org/jira/secure/attachment/12714398/massembly-737.zip) (_2.22 kB_)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the WAR packaging described in the issue with the attached massembly-737.zip and compare its MANIFEST.MF with the Maven WAR Plugin output. Trace the assembly plugin's WAR and manifest handling; done means the generated WAR's default manifest entries match the expected behavior or the discrepancy is otherwise resolved.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.