maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andre Brait (Jira)" <j...@apache.org>
Subject [jira] [Commented] (MRESOURCES-254) Filtering of compound properties using properties added by other plugins fails without ${*} delimiter
Date Mon, 20 Jul 2020 11:42:00 GMT

    [ https://issues.apache.org/jira/browse/MRESOURCES-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17161168#comment-17161168
] 

Andre Brait commented on MRESOURCES-254:
----------------------------------------

Sorry, I didn't get that you were still using my example.

Yes, compound properties themselves are ok. It's only an issue if the properties have been
added by a plugin.

> Filtering of compound properties using properties added by other plugins fails without
${*} delimiter
> -----------------------------------------------------------------------------------------------------
>
>                 Key: MRESOURCES-254
>                 URL: https://issues.apache.org/jira/browse/MRESOURCES-254
>             Project: Maven Resources Plugin
>          Issue Type: Bug
>          Components: delimiters, filtering
>    Affects Versions: 3.1.0
>            Reporter: Andre Brait
>            Priority: Major
>         Attachments: test.zip
>
>
> How to reproduce:
>  # Open the project I attached here
>  # Run mvn clean compile
>  # Check that the file target/classes/someText.txt has a compund property that was incorrectly
filtered
>  # SetĀ useDefaultDelimiters to true and run mvn clean compile again
>  # Check that the fileĀ target/classes/someText.txt was now filtered properly



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

Mime
View raw message