${maven.build.timestamp} not being properly resolved during WST server run

Using latest eclipse 3.7 kepler with latest GPE 1.8.3...

In my war pom.xml... I have something like this:

    <properties>
        <maven.build.timestamp.format>yyyy-MM-dd-HHmm</maven.build.timestamp.format>
        <appengine.app.version>${maven.build.timestamp}</appengine.app.version>
                <appengine.app.name>voostip</appengine.app.name>
        <appengine.target.version>1.8.3</appengine.target.version>
    </properties>

In my appengine-web.xml I have this:

    <application>${appengine.app.name}</application>
    <version>${appengine.app.version}</version>

I setup WST with a Server. I then hit the play button for that server.

The appengine-web.xml that is copied into the WST folder  
(/Users/jon/Documents/workspace/.metadata/.plugins/org.eclipse.wst.server.core/t
mp0/voost-ip-webapp/WEB-INF) looks like this:

        <application>voostip</application>
        <version>${maven.build.timestamp}</version>

Notice that it is resolved as ${maven.build.timestamp}.

This article explains that it should work: 
http://stackoverflow.com/questions/13228472/how-to-acces-maven-build-timestamp-f
or-resource-filtering

Original issue reported on code.google.com by latch...@gmail.com on 2 Sep 2013 at 12:13

dkuspawono / google-plugin-for-eclipse

${maven.build.timestamp} not being properly resolved during WST server run #235