[
https://jira.codehaus.org/browse/MASSEMBLY-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335136#comment-335136
]
Steve Cohen commented on MASSEMBLY-670:
---------------------------------------
I realized that I could test this easily enough even with your git setup. I
manually touched one file in the src/conf directory with a 2004 timestamp and
found that the archive did reflect the changed timestamp.
So what is the difference?
My real situation is using apache-maven-3.0.5, my test situation is using
3.0.4, not likely to be relevant.
Both situations use the assembly plugin version 2.4
My real situation is using jdk 1.6, the test situation is using 1.7
The real situation is using RHEL 5.0, the test situation is using Ubuntu 13.04
The only one of these I could possibly see as being relevant is the jdk.
> assembly plugin tar.gz format does not preserve timestamps of files it adds
> to archive
> --------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-670
> URL: https://jira.codehaus.org/browse/MASSEMBLY-670
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Components: component descriptor
> Affects Versions: 2.4
> Environment: linux
> Reporter: Steve Cohen
>
> The .tar.gz archives created by the assembly plugin do not preserve the
> timestamps of the files it adds to the archive. There is no setting to
> override this.
> This differs from the functionality of the tar program. That program
> preserves timestamps by default, when adding to the archive and there is no
> option to change this, although there are options to change the timestamps on
> extraction.
> The maven plugin should emulate tar here, I would think.
--
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
