[
https://issues.apache.org/jira/browse/MRESOURCES-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17161120#comment-17161120
]
Dennis Lundberg commented on MRESOURCES-254:
--------------------------------------------
Hi,
I can confirm the results in your test project.
However if I add this property to the pom.xml
{code:xml}
<prop6>${prop1}-${prop2}</prop6>
{code}
and this to src/main/resources/someText.txt
{noformat}
But this does: @prop6@
{noformat}
the output for prop6 is correct, even when I set useDefaultDelimiters to false.
So maven-resources-plugin does have support for compound properties.
This makes me suspect that it might have something to do with
buildnumber-maven-plugin, but I haven't investigated that.
> 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)
