[
http://jira.codehaus.org/browse/MSITE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MSITE-264.
---------------------------------
Assignee: Dennis Lundberg
Resolution: Won't Fix
This will not work because Velocity is used to do the filtering. I have added a
section to the usage documentation about this.
> Property names with periods are not resolved
> --------------------------------------------
>
> Key: MSITE-264
> URL: http://jira.codehaus.org/browse/MSITE-264
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Reporter: Cameron Jones
> Assignee: Dennis Lundberg
>
> I've been trying to get property filtering to work over the site documents as
> specified in http://maven.apache.org/plugins/maven-site-plugin/usage.html by
> appending the '.vm' extension to the appropriate files. The problem is that
> the property filtering doesn't seem to work when the property names contain
> periods for breaking up the context words, for example:
> The works:
> ${currentVersion}
> This doesn't:
> ${current.version}
> For some reason the default maven properties which are always available do
> work even if they have periods, for example this is resolved correctly:
> ${project.version}
--
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
