[ https://issues.apache.org/jira/browse/MWAR-415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte updated MWAR-415: -------------------------------- Description: It may be related to MRESOURCES-99 When a webResource, with filtering enabled contains property ${maven.build.timestamp}, it's not replaced by the timestamp. The workaround is to remove definitions of webResource and configure the resources on <build><resources> level (and making sure that maven-resource-plugin version is >= 3.0.0) was: It may be related to https://issues.apache.org/jira/browse/MRESOURCES-99 When a webResource, with filtering enabled contains property ${maven.build.timestamp}, it's not replaced by the timestamp. The workaround is to remove definitions of webResource and configure the resources on <build><resources> level (and making sure that maven-resource-plugin version is >= 3.0.0) > ${maven.build.timestamp} is not working in filtered webResources > ---------------------------------------------------------------- > > Key: MWAR-415 > URL: https://issues.apache.org/jira/browse/MWAR-415 > Project: Maven WAR Plugin > Issue Type: Bug > Affects Versions: 3.2.0 > Reporter: Leonid Rozenblyum > Priority: Major > > It may be related to MRESOURCES-99 > When a webResource, with filtering enabled contains property > ${maven.build.timestamp}, it's not replaced by the timestamp. > The workaround is to remove definitions of webResource and configure the > resources on <build><resources> level (and making sure that > maven-resource-plugin version is >= 3.0.0) -- This message was sent by Atlassian Jira (v8.3.4#803005)