[jira] [Issue Comment Deleted] (JCRVLT-389) Optionally support Maven Filtering during packaging

["Konrad Windszus (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/JCRVLT-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konrad Windszus updated JCRVLT-389:
-----------------------------------
    Comment: was deleted

(was: I think there is a misunderstanding: The f-p-m-p takes all source files from the first folder found with a name given in parameter {{jcrRootSourceDirectory}}. In your case this is not overwritten so the default is taken (i.e. {{${project.basedir}/jcr_root}}). Everything below that folder covered by a filter rule is added to the content package. Therefore both subfolders (clientlibs and core) are added to your package. )

> Optionally support Maven Filtering during packaging
> ---------------------------------------------------
>
>                 Key: JCRVLT-389
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-389
>             Project: Jackrabbit FileVault
>          Issue Type: Improvement
>          Components: package maven plugin
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>            Priority: Major
>             Fix For: package-maven-plugin-1.1.0
>
>         Attachments: 191227_myproject1-ui.apps-1.0.0-SNAPSHOT.zip
>
>
> In some cases it would be useful to apply some filtering before a file is being included in the package. Instead of filtering it as separate goal via copy resources this filtering should be optionally supported by the package goal (similar to what the maven-war-plugin offers in https://maven.apache.org/plugins/maven-war-plugin/examples/adding-filtering-webresources.html)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)