[
http://jira.codehaus.org/browse/MWAR-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Petr Kozelka closed MWAR-108.
-----------------------------
Resolution: Fixed
oops... I actually edited different POM which of course had no impact on
observed war :-)
In fact, the "archive" parameter influences both the WAR's MANIFEST.MF, and the
one in JAR created from archived classes.
This probably is not the right thing anyway, but definitely a different
bugreport.
> parameter "archive" not respected - no way to influence MANIFEST.MF
> -------------------------------------------------------------------
>
> Key: MWAR-108
> URL: http://jira.codehaus.org/browse/MWAR-108
> Project: Maven 2.x War Plugin
> Issue Type: Bug
> Affects Versions: 2.0.2
> Reporter: Petr Kozelka
>
> There seems to be no way to influence the war's MANIFEST.MF . At least the
> expected way is not working:
> {quote}
> ...
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-war-plugin</artifactId>
> <configuration>
> <archive>
> {color:red}<manifest>
>
> <addDefaultSpecificationEntries>true</addDefaultSpecificationEntries>
>
> <addDefaultImplementationEntries>true</addDefaultImplementationEntries>
> </manifest>
> <manifestEntries>
> <Specification-Title>${artifactId}</Specification-Title>
> </manifestEntries>
> {color}
> </archive>
> </configuration>
> </plugin>
> ...
> {quote}
> This configuration does not change anything in the resulting
> {{xyz.war!/META-INF/MANIFEST.MF}}
--
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
