-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Maven 3.0.1, Hudson 1.394
Steps to reproduce:
0. Create a simple maven 3 project
1. Enable Resource Filtering
2. Add a resource file with this content:
SERVER_VERSION=${project.version}
SERVER_BUILD_DATE=${timestamp}
3. Add a property to the pom (to work around http://jira.codehaus.org/browse/MRESOURCES-99)
<properties>
<timestamp>${maven.build.timestamp}</timestamp>
</properties>
4. Executing mvn help:effective-pom shows
- The WRONG Result on hudson: .... <timestamp>${maven.build.timestamp}</timestamp> ....
- The correct Result when you run it on a local machine: <timestamp>20110121-1512</timestamp>
5. Because of the behavior described in step 4 the resource filtering is not working as expected:
SERVER_VERSION=2.3.0-SNAPSHOT
SERVER_BUILD_DATE=${maven.build.timestamp}
- is related to
-
JENKINS-9693 maven.build.timestamp.format is not obeyed in maven builds
-
- Resolved
-
[JENKINS-8573] Replacement of some maven properties is not working
Assignee | New: Olivier Lamy [ olamy ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Link |
New:
This issue is related to |
Component/s | New: maven-plugin [ 16033 ] | |
Component/s | Original: maven2 [ 15487 ] |
Workflow | Original: JNJira [ 138684 ] | New: JNJira + In-Review [ 188106 ] |