[
http://jira.codehaus.org/browse/MWAR-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=231977#action_231977
]
Benson Margulies commented on MWAR-230:
---------------------------------------
Hmm. It's an awfully useful working directory. I'm using it for jetty:run,
since it has the overlays.
I guess I'm supposed to add an execution of the unpacked target instead.
> archive configuration ignored for unpacked war
> ----------------------------------------------
>
> Key: MWAR-230
> URL: http://jira.codehaus.org/browse/MWAR-230
> Project: Maven 2.x WAR Plugin
> Issue Type: Bug
> Affects Versions: 2.1-alpha-2
> Reporter: Benson Margulies
>
> I have added configuration information to my POM to add an entry to my WAR's
> manifest.
> And, indeed, it appears correctly in the manifest in the .war file.
> However, there is also an unpacked war that is delivered by default. It also
> has a manifest, and that manifest does not include my extra entry.
> Since all of this results from the default execution from
> <packaging>war</packaging> I don't see where else I should have to add this
> configuration.
> {code}
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-war-plugin</artifactId>
> <configuration>
> <archive>
> <manifest>
> <addDefaultImplementationEntries>true</addDefaultImplementationEntries>
> </manifest>
> <manifestEntries>
> <Implementation-Build>${buildNumber}</Implementation-Build>
> </manifestEntries>
> </archive>
> <overlays>
> <overlay>
> <groupId>com.basistech.jug</groupId>
> <artifactId>gate-home</artifactId>
> <classifier>gate-home</classifier>
> <type>zip</type>
> <targetPath>WEB-INF</targetPath>
> </overlay>
> </overlays>
> </configuration>
> </plugin>
> {code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
