[
https://issues.apache.org/jira/browse/MRESOURCES-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17162026#comment-17162026
]
Dennis Lundberg commented on MRESOURCES-254:
--------------------------------------------
Thanks for clarifying. That certainly looks like a valid use case.
I am not a developer on Maven core, but I don't see any other way for than to
duplicate that property. Once using @@ for maven-resources-plugin and another
using ${} for other plugin configuration in the POM.
You can read about model interpolation here:
[https://maven.apache.org/ref/3.6.3/maven-model-builder/]
That describes when the replacement of ${...} in the POM occurs.
> 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-updated.zip, 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)
