Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
2.4.1
-
None
-
None
-
None
-
Maven 2.2.1
Windows XP
Description
As I upgraded the maven-resources-plugin to version 2.4.1 (version 2.3 has a major issue concerning windows paths, see http://jira.codehaus.org/browse/MRESOURCES-81), I'm facing another problem with default filtering delimiters.
If one of the resources contains a delimiter character that is not part of an expandable expression, then all of the following expandable expressions after the character will not be processed.
You can reproduce this using a resource property file that contains the default '@' character delimiter:
Contact: ${pom.name}@mycompany.com URL: ${pom.url} Version: ${pom.version}
Processing the project resources with Maven will produce:
Contact: myapp@myorganization.com URL: ${pom.url} Version: ${pom.version}
If the '@' delimiter character is removed, then it produces a correct output:
Contact: myappmycompany.com
URL: http://maven.apache.org
Version: 1.0
I tried to configure the plugin but it seems that I'm not able to redefine/disable/remove the default delimiters.
This bug was not present in version 2.3 but, as said before, this version has know bugs with windows paths (even if I hope that in future releases, my application will no more reference windows paths...).
Thanks for your support!
Attachments
Issue Links
- duplicates
-
MRESOURCES-104 while filtering resources the token replacement stops at the character @
- Closed
- relates to
-
MRESOURCES-117 maven-resources-plugin 2.4+ filtering broken
- Closed