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...@codehaus.org> on 2014/11/25 21:32:04 UTC

[jira] (MECLIPSE-588) Web resource with filtering selected is copied to server without filtering.

     [ https://jira.codehaus.org/browse/MECLIPSE-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MECLIPSE-588.
-----------------------------------

    Resolution: Won't Fix

Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.

> Web resource with filtering selected is copied to server without filtering.
> ---------------------------------------------------------------------------
>
>                 Key: MECLIPSE-588
>                 URL: https://jira.codehaus.org/browse/MECLIPSE-588
>             Project: Maven Eclipse Plugin
>          Issue Type: Bug
>          Components: WTP support
>    Affects Versions: 2.7
>         Environment: Win x64 JSE 1.6 MVN 2.20
>            Reporter: Ian Carr
>
> I have the following in my pom:
> <plugin>
>                 <artifactId>maven-war-plugin</artifactId>
>                 <configuration>
>                     <webResources>
>                         <resource>
>                             <directory>configurations/tomcat</directory>
>                             <filtering>true</filtering>
>                         </resource>
>                     </webResources>
> The resource directory contains a config.xml which requires substitutions hence the filtering true.
> This is now being  added into the eclipse org.eclipse.wst.common.component file as follows
>   <wb-module deploy-name="ClientMainWeb">
>     <property name="context-root" value="ClientMainWeb"/>
>     <wb-resource deploy-path="/" source-path="src/main/webapp"/>
>     <wb-resource deploy-path="/" source-path="configurations/tomcat"/>
> Which I believe triggers the copying of the content of the folder into the published web application directory. Unfortunately
> the filtering does not occur and I end up with a non-viable context.xml.
> I presume the plugin should ignore resource marked as requiring filtering and allow the user to apply a work around or
> perform the filtering operation into another location and add this other location to the file rather than the original unfiltered version.
> Many thanks



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)