[ 
https://jira.codehaus.org/browse/MWAR-301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=333877#comment-333877
 ] 

Juan Miguel Bernal Gonzalez edited comment on MWAR-301 at 10/9/13 11:25 AM:
----------------------------------------------------------------------------

I've the same issue.

The problem is that the maven-filtering doesn't get the default base filter 
(declared in <build> tag) of the project *pom.xml*.

For a workaround, you have to add a *<filters>* tag in *<configuration>*, again:

{code:borderStyle=solid}
<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-war-plugin</artifactId>
    <version>2.4</version>
    <configuration>
        ...
        <filters>
            
<filter>${project.basedir}/src/main/filters/my-filter.properties</filter>
        </filters>
        
    </configuration>
</plugin>
{code}

                
      was (Author: juanmiguelbg):
    I've the same issue.

The problem is that the maven-shade doesn't get the default base filter 
(declared in <build> tag) of the project *pom.xml*.

For a workaround, you have to add a *<filters>* tag in *<configuration>*, again:

{code:borderStyle=solid}
<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-war-plugin</artifactId>
    <version>2.4</version>
    <configuration>
        ...
        <filters>
            
<filter>${project.basedir}/src/main/filters/my-filter.properties</filter>
        </filters>
        
    </configuration>
</plugin>
{code}

                  
> webResources filtering not happening properly
> ---------------------------------------------
>
>                 Key: MWAR-301
>                 URL: https://jira.codehaus.org/browse/MWAR-301
>             Project: Maven WAR Plugin
>          Issue Type: Bug
>          Components: filtering
>    Affects Versions: 2.4
>         Environment: Linux
>            Reporter: Mukarram Baig
>         Attachments: mwar-tester.zip
>
>
> I noticed that webResources were not getting filtered when I upgraded from 
> 2.3 to 2.4 and could not find an open issue related to it, so letting you 
> guys know if I am doing something incorrect that was working till 2.3 and got 
> fixed in 2.4. I am attaching a sample project where a JS file was getting 
> filtered properly when using 2.3 and not when using 2.4.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to