Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Won't Fix
-
2.2-beta-2
-
None
-
None
-
Win32, Maven 2.0.9
Description
A resource file (a Unix shell file) with this definition
: ${BASE_DIR:=..}
results in this after being filtered by the assembly plugin
: MavenProject: catmktg:FlexRxProject:T1.4.0 @ F:\FlexRx\checkouts\pom.xml
The expectation is that '..' would be left alone as there is no definition for this in our context. Turns out there is in ${project}, however. Specifying ${.url} and ${.file}, etc. result in replacements same as ${project.url} and ${project.file} as well. This seems like a bug but perhaps it is a feature that needs some refinement.
The workaround in our case is to quote the dots ('..') which works when using it in a Unix path. However, this may not suffice in other cases.
I've seen similar reports in MWAR-133 and MRESOURCES-20 but I cannot find a report in MASSEMBLY.
Attachments
Issue Links
- is related to
-
MASSEMBLY-385 Filtering replaces tokens it should not be replacing
- Closed
- relates to
-
MRESOURCES-20 Filtering ${foo.file} evaluates to in full path to pom.xml
- Closed
-
MWAR-133 Filtering issue: wrong replacement of properties by values from MavenProject object
- Closed