${project.baseUri} and ${maven.build.timestamp} are not expanded by resource filtering

where does project.baseUri come from?

$

comes from the documentation
and from this bug : MNG-3760.

actually, the Version 2.2 is also affected

Workaroung: add following property

<properties>
  <timestamp>${maven.build.timestamp}</timestamp>
</properties>

and after that you can reference it within resource.

I couldn't get Evgeny's workaround to work on Maven 3.0-alpha-7 and 3.0-beta-1. According to help:effective-pom the property {{$

}} does get interpolated in the POM, but resource filtering (which affects the file in question, at least according to mvn -X) doesn't work.

Actually, me last comment isn't true; the workaround does work with Maven 3.

What happened was this: I followed the advice of http://maven.apache.org/shared/maven-archiver/examples/manifestFile.html and got burned by the fact that the manifest file include was the one from the unfiltered source directory rather than from the filtered target directory.

The workaround mentioned by Evgeny seems to be dependent on environment.

It works on my windows machine:
Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
Java version: 1.6.0_23, vendor: Sun Microsystems Inc.
Java home: c:\progs\java\jdk1.6.0_23_32bit\jre
Default locale: cs_CZ, platform encoding: Cp1250
OS name: "windows 7", version: "6.1", arch: "x86", family: "windows"

effective pom:
<timestamp>20110325-1614</timestamp>

But does not work on Jenkins CI server with Debian:
Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
Java version: 1.6.0_22, vendor: Sun Microsystems Inc.
Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "2.6.18.8-xenu", arch: "amd64", family: "unix"

effective pom:
<timestamp>$

</timestamp>

@Petr see http://issues.jenkins-ci.org/browse/JENKINS-8573

I would close this issue, as it has been fixed, as Olivier Lamy has shown. I have confirmed that <timestamp>${maven.build.timestamp}</timestamp> works.

I'm not sure that issue should be closed, because definition of a new property - it's just a workaround for original problem.

I agree; it worries me that some properties are visible in the POM but not in the resource plugin. What is causing this? Are there two types of properties?

@Aaron/@Evgeny: Yeah, I revise what I said. You guys are right: this should stay open.

Just ran into this issue today. It's a pity it isn't solved after more than three years
Is backwards-compatibility to Maven 2.x important at this point?
When upgrading to Maven 3.x, man could somehow use a

src.main.java.org.apache.maven.model.interpolation.BuildTimestampValueSource

https://git-wip-us.apache.org/repos/asf?p=maven.git;a=blob;f=maven-model-builder/src/main/java/org/apache/maven/model/interpolation/BuildTimestampValueSource.java

I think someone who's familiar with building maven plugins (which excludes me ) could do this in very little time...