Issue Details (XML | Word | Printable)

Key: MSHARED-60
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Critical Critical
Assignee: Olivier Lamy
Reporter: Olivier Lamy
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Maven Shared Components

Filtering ${foo.file} evaluates to in full path to pom.xml

Created: 06/Sep/08 03:40 PM   Updated: 11/Sep/08 10:18 AM   Resolved: 06/Sep/08 04:34 PM
Return to search
Component/s: None
Affects Version/s: maven-filtering-1.0-beta-1
Fix Version/s: maven-filtering-1.0-beta-2

Time Tracking:
Not Specified

Environment: Windows XP, Maven 2.0.2
Issue Links:
Duplicate
 
Related
 
dependent
 


 Description  « Hide

If an unresolved variable is encountered, the plugin simply does not replace the variable in the target file.
If this unresolved variable however ends in ".file}" it will evaluate to a file object that targets the current pom. This results in the replacement being the complete path to that pom (in the 2.1 version of the plugin this results in a ClassCastException).

The workaround is, of course, not to filter the affected files.
Though this will not work if other variables in the affected files do need to be replaced.



Olivier Lamy added a comment - 06/Sep/08 04:34 PM

fixed in rev 692742