[
https://jira.codehaus.org/browse/MRESOURCES-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=327067#comment-327067
]
Gareth Smith commented on MRESOURCES-168:
-----------------------------------------
I think this feature would be great. It would be similar to how ANTs replace
task works - http://ant.apache.org/manual/Tasks/replace.html.
This bug on PLXUTILs is slightly related:
http://jira.codehaus.org/browse/PLXUTILS-139
> Don't overwrite unchanged resource to prevent unnecessary subsequent
> processing
> -------------------------------------------------------------------------------
>
> Key: MRESOURCES-168
> URL: https://jira.codehaus.org/browse/MRESOURCES-168
> Project: Maven 2.x Resources Plugin
> Issue Type: Improvement
> Components: filtering
> Environment: MVN3.0.4 Win7 Pro SP1 64 Bit JDK 1.6.0_07
> Reporter: Markus KARG
> Priority: Minor
>
> When filtering resources, the resulting files' last-modified date is updated.
> This is correct, as the file just got produced. But, there might be lots of
> files that passed the filter unchanged -- but now have changed last-modified
> date, too.
> This induces unneccesary subsequent processing and should be prevented.
> Example: Filtering of Java sources, then compiling those. The Java compiler
> typically will only compile modified files, but not thinks ALL files are
> modified.
> A solution could be to check whether at least one property was actually found
> in the filtered file and to reset the last-modified date in all other cases.
> Another solution could be to rename the previous output file and compare both
> files after filtering. If they are identical, the new fill can be discarded
> and the previous file can be renamed back.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
