[
https://issues.apache.org/jira/browse/MWAR-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17153275#comment-17153275
]
Martin Höller commented on MWAR-433:
------------------------------------
This branch works for me.
FYI: my problem was with CSS/LESS resources that were processes by the
[lesscss-maven-plugin
[https://github.com/marceloverdijk/lesscss-maven-plugin].] With your changes,
the CSS resources are now included in the WAR, as expected.
One note to the changes: would it make sense to not hardcode "WEB-INF" but make
it configurable via a parameter? I also think that "WEB-INF/lib" might even be
a better choice.
hth,
- martin
> Maven WAR plugin is deleting files generated by other plugins after upgrading
> to 3.3.0
> --------------------------------------------------------------------------------------
>
> Key: MWAR-433
> URL: https://issues.apache.org/jira/browse/MWAR-433
> Project: Maven WAR Plugin
> Issue Type: Bug
> Affects Versions: 3.3.0
> Reporter: Kyle Lieber
> Priority: Critical
> Fix For: 3.3.1
>
>
> My project generates wsdls using the {{jaxws-maven-plugin}} which puts the
> generated wsdls in
> {{${project.build.directory}/${project.build.finalName}/WEB-INF/wsdls}} so
> that they are packaged up in the war file. Then I have a client jar that
> copies those wsdls out of the war file using the {{maven-dependency-plugin}}
> and generates a client from the wsdls using the {{jaxws-maven-plugin}}.
> This all works fine using {{3.2.3}} of the {{maven-war-plugin}}. However,
> after upgrading to {{3.3.0}} my project fails to build because the wsdls are
> no longer preserved. It seems that they are being deleted by the
> {{maven-war-plugin}}.
> I created an example project on Github which recreates the problem. The
> {{master}} branch is using {{3.2.3}} and the {{maven-war-plugin-3.3.0}}
> branch is using {{3.3.0}}. You can find more details in the readme file of
> the example project:
> https://github.com/klieber/maven-war-plugin-bug
> I also suspect that MWAR-427 is the change that introduced this bug.
> Please let me know if there is anymore information I can provide. Thanks!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
