Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.2, 2.3
-
Fix Version/s: 2.3
-
Component/s: None
-
Labels:None
-
Environment:OS: Windows XP; Maven: 2.0.5, 2.0.6;
-
Number of attachments :
Description
For exemple consider this in a filtered property files
application.propertyOne=$
{pom.build.directory}application.propertyTwo=$
{basedir}which generates after filtering:
application.propertyOne=D\:\\ProjectsDirectory\\project
target
application.propertyTwo=D:\ProjectsDirectory\project\
Behavior are different and causes a second property bad value when reading the properties file.
Issue Links
- depends upon
-
MRESOURCES-56
use (and release) the maven-filtering component
-
- relates to
-
MSHARED-78
FilteringUtils escapeWindowsPath() doesn't work on Windows
-
Patch for 2.3. In ReflectionProperties.java, add a test that enable backslashes escaping if the result of ReflectionValueExtractor.evaluate is a file