[
http://jira.codehaus.org/browse/MNG-5110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269330#action_269330
]
Karl M. Davis commented on MNG-5110:
------------------------------------
This can be worked around by adding a property to the POM whose value is set
using this property, e.g.:
{code:title=pom.xml}
<project>
<properties>
<myProperty>${project.baseUri}</myProperty>
</properties>
</project>
{code}
With that in place, $\{myProperty\} can be used in resources, like this:
{code:title=myResource.properties}
# Uses the ${myProperty} property in lieu of ${project.baseUri}, which is broken
myKey=${myProperty}
{code}
> Support ${project.baseUri} in resource filtering
> ------------------------------------------------
>
> Key: MNG-5110
> URL: http://jira.codehaus.org/browse/MNG-5110
> Project: Maven 2 & 3
> Issue Type: Sub-task
> Affects Versions: 3.0.3
> Environment: Windows 7, 32-bit Java 6 JRE (Oracle)
> Reporter: Karl M. Davis
>
> Though the {{${project.baseUri}}} property does work in POMs, it does not
> appear to be working for resource filtering.
--
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
