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

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.6
• Fix Version/s: 2.6
• Component/s: manifest
• Flags: Patch
• Assignee: Unassigned
• Reporter: Jakub Bochenski
• Created: 17/Aug/15 15:12
• Updated: 13/Nov/19 18:52

Description

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

<goals> 
  <goal>exploded</goal> 
</goals>

to

<goals> 
  <goal>manifest</goal> 
  <goal>exploded</goal> 
</goals>

and add the generated files to SCM ignore.

Issue Links

• is duplicated by: MWAR-418 Manifest not written to exploded location
• is related to: MWAR-167 Final manifest not written to exploded location
• is related to: MWAR-197 war:manifest does not add "manifestEntries" to generated manifest
• relates to: MWAR-379 manifest goal violates general Maven principle and creates file into src/main/..