Filtered resources should support ${pom.*} and ${project.*} syntax only, not
${*}, for POM properties
-----------------------------------------------------------------------------------------------------
Key: MNG-609
URL: http://jira.codehaus.org/browse/MNG-609
Project: Maven 2
Type: Bug
Versions: 2.0-alpha-3
Environment: Maven 2.0-alpha-3, WinXP SP2, Java 1.5.0_02
Reporter: John Fallows
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 has the added benefit of reduced collision space for top-level variables
in filtered resource files.
Recommend that top level variables, such as ${version} are _not_ supported as
implicit filter variables, only ${pom} and ${project}.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
