[
http://jira.codehaus.org/browse/MASSEMBLY-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161900#action_161900
]
Mickaël Floc'hlay commented on MASSEMBLY-363:
---------------------------------------------
I think the priority of this issue should be higher than "minor".
In my case, I have a to-be-filtered file in which i wrote
something.name=${something.name}
which results, after being filtered by the assembly plugin, to :
something.name=<the content of my pom file pom.name>
This occurs whether a property something.name is set in the filtering file or
not.
As naming a property .name is pretty current, this issue can be really annoying
and should be resolved with a higher priority.
Mick.
> Filter replaces all variables ending in ., .url, .file, etc. with
> corresponding value from POM
> ----------------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-363
> URL: http://jira.codehaus.org/browse/MASSEMBLY-363
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-2
> Environment: Win32, Maven 2.0.9
> Reporter: Stephen Robinson
> Priority: Minor
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
