Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.2
-
Fix Version/s: 2.3
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
It should be possible to control the order in which resource directories are copied to target/classes, since multiple resource dirs could potentially contain files with the same names. The intutive thing would be to copy the resource directories in the order they are specified in the POM (i.e. last one wins). However, it appears the resources are currently copied in reverse order (i.e. first one wins).
Issue Links
| This issue is duplicated by: | ||||
| MRESOURCES-43 | resources:resources overwrites destination files when filtering is on, not when filtering is off |
|
|
|
| MRESOURCES-24 | Force overwrite resources defined in profiles |
|
|
|
| This issue depends upon: | ||||
| MSHARED-67 | Add a parameter to force overwrite existing files even if the destination files are newer |
|
|
|
Activity
Hide
Olivier Lamy
added a comment -
fixed in rev 695036.
There is now a flag called overwrite in the mojo and is false by default (you have to change it manually to true)
IMHO this flag can be added in the Resource class but it's an other story 
Show
Olivier Lamy
added a comment - fixed in rev 695036.
There is now a flag called overwrite in the mojo and is false by default (you have to change it manually to true)
IMHO this flag can be added in the Resource class but it's an other story
If your resources have filtering to true : last one always wins.
If not : there is a test on file.lastModified (to.lastModified() < from.lastModified()) .
IMHO we should probably add a new flag "overwrite" (Overwrite existing files even if the destination files are newer.) in the mojo