jira-importer opened a new issue, #135: URL: https://github.com/apache/maven-war-plugin/issues/135
**[Fred Bricon](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=fbricon)** opened **[MWAR-306](https://issues.apache.org/jira/browse/MWAR-306?redirect=false)** and commented If you try to filter a file containing say : > ${project.artifactId} @ ${project.version} 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 --- **Affects:** 2.4 **Attachments:** - [web-filtering.zip](https://issues.apache.org/jira/secure/attachment/12720578/web-filtering.zip) (_1.43 kB_) **Issue Links:** - [MWAR-313](https://issues.apache.org/jira/browse/MWAR-313) Upgrade maven-filtering to 1.2 (_**"depends upon"**_) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
