elharo commented on issue #182:
URL: 
https://github.com/apache/maven-war-plugin/issues/182#issuecomment-5142716693

   The problem stems from how the `maven-war-plugin` currently orders its 
operations. When running `war:exploded`, it creates the exploded directory 
structure first. It then uses that exploded directory as the input for 
generating the final WAR file (`war:war`).
   
   The plugin's internal architecture delegates the creation of the 
`MANIFEST.MF`, `pom.xml`, and `pom.properties` files exclusively to the final 
archiving step. Because these files are generated and injected directly into 
the compressed archive by the Maven Archiver, they are never written back to 
the exploded directory.
   
   Fixing this would require a substantial rewrite of the plugin's internal 
workflow so that all metadata files are generated in the exploded directory 
prior to archiving, rather than injecting them during the compression phase.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to