[
https://issues.jboss.org/browse/SHRINKWRAP-378?page=com.atlassian.jira.pl...
]
Tair Sabirgaliev edited comment on SHRINKWRAP-378 at 1/31/12 8:43 AM:
----------------------------------------------------------------------
Found a workaround for now:
Manually generate manifest in src/main/webapp/META-INF/MANIFEST.MF
mvn war:manifest
Now tests pass
mvn package integration-test
was (Author: tair.sabirgaliev):
Found a workaround for now:
mvn war:manifest
mvn package
integration-test
MavenImporter does not import MANIFEST.MF file
----------------------------------------------
Key: SHRINKWRAP-378
URL:
https://issues.jboss.org/browse/SHRINKWRAP-378
Project: ShrinkWrap
Issue Type: Bug
Components: ext-resolver
Affects Versions: resolver-1.1.0-alpha-2
Reporter: Karel Piwko
MavenImporter packages intermediate results from target directory of a Maven project.
However, for MANIFEST.MF, this file is added later on during package phase, so it is not
included in the file.
Solving this issue is cumbersome, because this file is created as the archive is
constructed. We have to somehow emulate Maven archiver to get the file before the
jar/war/ear packaging is done.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira