[
https://issues.apache.org/jira/browse/MWAR-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakub Bochenski updated MWAR-353:
---------------------------------
Description:
If I have no manifest files I don't get anything in the exploded location.
If I put a {{MANIFEST.MF}} under webapp folder's {{META-INF/MANIFEST.MF}} I
just get the static file.
If I set {{archive/manifestFile}} to point at some file I just get the static
file.
Workaround: change
{code}
<goals>
<goal>exploded</goal>
</goals>{code}
to
{code}
<goals>
<goal>manifest</goal>
<goal>exploded</goal>
</goals>{code}
and add the generated files to SCM ignore.
was:
If I have no manifest files I don't get anything in the exploded location.
If I put a {{MANIFEST.MF}} under webapp folder's {{META-INF/MANIFEST.MF}} I
just get the static file.
Workaround: change
{code}
<goals>
<goal>exploded</goal>
</goals>{code}
to
{code}
<goals>
<goal>manifest</goal>
<goal>exploded</goal>
</goals>{code}
and add the generated files to SCM ignore.
> Manifest still not written to exploded location
> -----------------------------------------------
>
> Key: MWAR-353
> URL: https://issues.apache.org/jira/browse/MWAR-353
> Project: Maven WAR Plugin
> Issue Type: Bug
> Components: manifest
> Affects Versions: 2.6
> Reporter: Jakub Bochenski
> Assignee: Karl Heinz Marbaise
> Fix For: 2.6
>
>
> If I have no manifest files I don't get anything in the exploded location.
> If I put a {{MANIFEST.MF}} under webapp folder's {{META-INF/MANIFEST.MF}} I
> just get the static file.
> If I set {{archive/manifestFile}} to point at some file I just get the static
> file.
> Workaround: change
> {code}
> <goals>
>
> <goal>exploded</goal>
> </goals>{code}
> to
> {code}
> <goals>
>
> <goal>manifest</goal>
>
> <goal>exploded</goal>
> </goals>{code}
>
> and add the generated files to SCM ignore.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
