[
http://jira.codehaus.org/browse/MNG-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=134057#action_134057
]
Ezra Jennings commented on MNG-3359:
------------------------------------
If you're having this problem with Freemarker templates, a workaround is to
replace:
${something.name}
with
${something.name?string}
and now Maven will not think it is a Maven variable.
> Filtering with POM.xml elements
> -------------------------------
>
> Key: MNG-3359
> URL: http://jira.codehaus.org/browse/MNG-3359
> Project: Maven 2
> Issue Type: Bug
> Components: POM
> Affects Versions: 2.0.8
> Reporter: Zach Legein
> Attachments: maven-bug.tar.gz
>
>
> I have this weird error where if I have a project like the one attached. It
> appears that when filtering is set to _true_ and you have an file that has a
> reference to a 'name' value, like so:
> {code:xml}
> <html>
> <head>
> <title>${something.name}</title>
> </head>
> </html>
> {code}
> The pom.xml _name_ element will be used when filtering this file.
> So if your pom.xml is written like so:
> {code:xml}
> <project>
> <name>Look at Me!</name>
> </project>
> {code}
> This _name_ value will be used to do filtering if turned on.
> Granted you would want to set up your project like this, but this is not
> expected behavior, right?
--
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
