[
https://jira.codehaus.org/browse/MRESOURCES-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=346918#comment-346918
]
Daniel Geißler commented on MRESOURCES-79:
------------------------------------------
Is there any example using the described process?
do you mean using different the plugin configurations for the
resources:testResources and resources:resources goals or is there a extension
to the inline declaration mentioned above?
> <resources> are filtered by test filters
> ----------------------------------------
>
> Key: MRESOURCES-79
> URL: https://jira.codehaus.org/browse/MRESOURCES-79
> Project: Maven Resources Plugin
> Issue Type: Bug
> Affects Versions: 2.3
> Environment: Maven 2.0.9, Java 1.6.0_07 OS_X
> Reporter: nodje
> Assignee: John Casey
> Fix For: 2.4
>
> Attachments: resources-testcase.zip
>
>
> With the following configuration I assume <resources> should get filtered by
> src/main/filters/* and <testResources> by src/test/filters/* :
> <filters>
> <filter>src/main/filters/dev.filter.properties</filter>
> <filter>src/test/filters/dev.filter.properties</filter>
> </filters>
> <resources>
> <resource>
> <directory>src/main/resources</directory>
> <filtering>true</filtering>
> </resource>
> </resources>
> <testResources>
> <testResource>
> <directory>src/test/resources</directory>
> <filtering>true</filtering>
> </testResource>
> </testResources>
> But all resources files end up being filtered by the src/test/filters/*.
> Attached is the simpliest Maven2 proect reproducing this behavior.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
