[
https://jira.codehaus.org/browse/MWAR-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fred Bricon updated MWAR-306:
-----------------------------
Description:
If you try to filter a file containing say :
{quote}$\{project.artifactId\} @ $\{project.version\}{quote}
It'll be rendered as 'foo @ $\{project.version\}', when you expect 'foo @
1.0.0'
This used to work in maven-war-plugin <= 2.3, so I suspect this is caused by
the upgrade to maven-filtering:1.1.
Note that this bug has affected filtering using maven-resource-plugin for quite
some time now, so the root cause is definitely somewhere in the filtering
component. Opening the bug here to keep track of the regression in m-w-p
was:
If you try to filter a file containing say :
{quote} ${project.artifactId} @ ${project.version}{quote}
It'll be rendered as 'foo @ ${project.version}', when you expect 'foo @ 1.0.0'
This used to work in maven-war-plugin <= 2.3, so I suspect this is caused by
the upgrade to maven-filtering:1.1.
Note that this bug has affected filtering using maven-resource-plugin for quite
some time now, so the root cause is definitely somewhere in the filtering
component. Opening the bug here to keep track of the regression in m-w-p
> [regression] Filtering doesn't work if a lone @ is found in a line to
> interpolate
> ---------------------------------------------------------------------------------
>
> Key: MWAR-306
> URL: https://jira.codehaus.org/browse/MWAR-306
> Project: Maven WAR Plugin
> Issue Type: Bug
> Components: filtering
> Affects Versions: 2.4
> Reporter: Fred Bricon
> Attachments: web-filtering.zip
>
>
> If you try to filter a file containing say :
> {quote}$\{project.artifactId\} @ $\{project.version\}{quote}
> It'll be rendered as 'foo @ $\{project.version\}', when you expect 'foo @
> 1.0.0'
> This used to work in maven-war-plugin <= 2.3, so I suspect this is caused by
> the upgrade to maven-filtering:1.1.
> Note that this bug has affected filtering using maven-resource-plugin for
> quite some time now, so the root cause is definitely somewhere in the
> filtering component. Opening the bug here to keep track of the regression in
> m-w-p
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
