I noticed that the latest code on the trunk adds support for filtered
resources, including the ability to refer to pom properties, in
addition to any filter properties defined in filter.properties.
For example:
src/main/resources/my-resource.txt
with contents
${version}
It seems that each property of the POM is exposed as an independent
top-level variable.
I was expecting the filtered resource file syntax to be...
${project.version}
...since that would be consistent with expressions used in the pom.xml
file, such as:
<sourceDirectory>${project.basedir}/src/main/java</sourceDirectory>
This would also seem to have the added benefit of reduced collision
space for top-level variables in filtered resource files.
Would it be reasonable to change the trunk to use the ${project.*}
syntax for filtered resources? Maybe it works this way already and I
just misread the code.
Let me know if I should file an issue or not on JIRA.
Kind Regards,
John Fallows.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
