apache / apache/maven-war-plugin

[MWAR-353] Manifest still not written to exploded location

Open
#182 8 comments 0 reactions 0 assignees View on GitHub
bug priority:major
Dominant language
Java
Stars
50
Forks
97
Avg merge
16h 49m
Merged PRs (30d)
3

Description

**[Jakub Bochenski](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jbochenski)** opened **[MWAR-353](https://issues.apache.org/jira/browse/MWAR-353?redirect=false)** and commented

If I have no manifest files I don't get anything in the exploded location.
If I put a `MANIFEST.MF` under webapp folder's `META-INF/MANIFEST.MF` I just get the static file.
If I set `archive/manifestFile` to point at some file I just get the static file.

Workaround: change

```xml

exploded

```

to

```xml

manifest
exploded

```

and add the generated files to SCM ignore.

---

**Affects:** 2.6

**Issue Links:**
- [MWAR-418](https://issues.apache.org/jira/browse/MWAR-418) Manifest not written to exploded location
(_**"is duplicated by"**_)
- [MWAR-379](https://issues.apache.org/jira/browse/MWAR-379) manifest goal violates general Maven principle and creates file into src/main/..

- [MWAR-167](https://issues.apache.org/jira/browse/MWAR-167) Final manifest not written to exploded location

- [MWAR-197](https://issues.apache.org/jira/browse/MWAR-197) war:manifest does not add "manifestEntries" to generated manifest

3 votes, 4 watchers

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.