You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Karl Heinz Marbaise (JIRA)" <ji...@apache.org> on 2016/05/11 18:23:12 UTC
[jira] [Commented] (MRESOURCES-221) Additional practices for
Filtering example page
[ https://issues.apache.org/jira/browse/MRESOURCES-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15280568#comment-15280568 ]
Karl Heinz Marbaise commented on MRESOURCES-221:
------------------------------------------------
This is also in line with [MNG-2478].
> Additional practices for Filtering example page
> -----------------------------------------------
>
> Key: MRESOURCES-221
> URL: https://issues.apache.org/jira/browse/MRESOURCES-221
> Project: Maven Resources Plugin
> Issue Type: Bug
> Affects Versions: 2.7
> Environment: n/a
> Reporter: Anders Hammar
> Priority: Minor
> Fix For: 3.0.0
>
>
> In the end of the Filtering example page (examples/filter.html), it shows an example of excluding binaries from being filtered. This text should mentioned default excluded extensions as well as the 'nonFilteredFileExtensions' configuration.
> Also, I use a different practice which I find easier for the users. Instead of defining two resource sections for the same folder (with exclude/include), I define a different folder ('resources-filtered') where alla resources will be filtered. The users then don't need to check the pom and possibly reconfigure when they add a new resource file (which they very often forget to). Add this (as the recommended) practice.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)