SHRINKWRAP-48 is related, but more addresses the easy addition/mutation of the manifest.
The JAR tool, for instance, automatically creates MANIFEST.MF when using -c.
Looks like our default action should be to do the same, if/when the archive is represented as(JavaArchive.class), else not?
I suggest it for every archive which extends ManifestContainer<?>.
Dig it. Should also be in the JavaDocs of these aggregate views.
Please open up a JIRA Feature Request.
I've created a ManifestAsset class that you can find on github:
Using it right now is possible to add all the main attributes in a JAR Manifest.
I did it for work and because I wanted to try git but I would be happy to contribute to the project and change whatever you think is wrong.
Thanks for the great work,