You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2015/09/06 22:45:04 UTC
[jira] [Closed] (MWAR-203) overlay to strip the original
path
[ https://issues.apache.org/jira/browse/MWAR-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov closed MWAR-203.
-------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still applies, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.
> overlay <include> to strip the original path
> --------------------------------------------
>
> Key: MWAR-203
> URL: https://issues.apache.org/jira/browse/MWAR-203
> Project: Maven WAR Plugin
> Issue Type: Improvement
> Components: overlay
> Environment: 2.1-beta-1
> Reporter: Adam Hamer
> Priority: Minor
>
> I have a base-war project which I'd like to overlay into my project-war. To avoid filename conflicts I use <targetPath>, but the result is project//targetPath/WEB-INF/... and I don't really want the WEB-INF in there. I came across this posting with the same issue: http://www.coderanch.com/t/447258/Ant-Maven-Other-Build-Tools/Maven-war-dependencies-moving-files.
> I also tried an assembly approach, but this also includes WEB-INF. Other ideas could include using the dependency plugin, antrun-plugin, cargo plugin or some other option? However, I would like to use jetty now that it is supporting overlays http://jira.codehaus.org/browse/JETTY-1027.
> Perhaps some mechanism like this could be added:
> under <includes> or <include>
> <excludePathPrefix>/WEB-INF/</excludePathPrefix> <!-- ignores the prefix given -->
> <excludePath>true</excludePath> <!-- copies only the filename -->
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)