maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ittay Dror (JIRA)" <j...@codehaus.org>
Subject [jira] (MRESOURCES-155) Add an option to NOT copy resources if the source haven't changed, even though the filtering is ON
Date Mon, 02 Jan 2012 12:02:02 GMT

    [ https://jira.codehaus.org/browse/MRESOURCES-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=287257#comment-287257
] 

Ittay Dror commented on MRESOURCES-155:
---------------------------------------

Another alternative is to create a signature for both timestamp and the filtering properties
(e.g., create sha1 from heir string representation). then put a file with this signature in
the target folder. on build, if the signature is different, re-run copy&filter and update
the signature.
                
> Add an option to NOT copy resources if the source haven't changed, even though the filtering
is ON
> --------------------------------------------------------------------------------------------------
>
>                 Key: MRESOURCES-155
>                 URL: https://jira.codehaus.org/browse/MRESOURCES-155
>             Project: Maven 2.x Resources Plugin
>          Issue Type: Improvement
>          Components: copy, filtering
>            Reporter: Liya Katz
>
> Coping resources during incremental build on big projects affects performance dramatically.
> It should be an option to stop coping filtered resources when the source is not newer
than the target, just like in case of resources that were not filtered. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message