You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Olivier Lamy (JIRA)" <ji...@codehaus.org> on 2008/02/29 01:11:28 UTC

[jira] Commented: (MRESOURCES-21) when pom specifies multiple resource directories, the directories should be copied in the order they are in the pom

    [ http://jira.codehaus.org/browse/MRESOURCES-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125525 ] 

Olivier Lamy commented on MRESOURCES-21:
----------------------------------------

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


> when pom specifies multiple resource directories, the directories should be copied in the order they are in the pom
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: MRESOURCES-21
>                 URL: http://jira.codehaus.org/browse/MRESOURCES-21
>             Project: Maven 2.x Resources Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2
>            Reporter: Ian Springer
>             Fix For: 2.3
>
>
> 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).

-- 
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