maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Cohen (JIRA)" <j...@codehaus.org>
Subject [jira] (MASSEMBLY-670) assembly plugin tar.gz format does not preserve timestamps of files it adds to archive
Date Mon, 04 Nov 2013 17:17:52 GMT

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

Steve Cohen edited comment on MASSEMBLY-670 at 11/4/13 11:16 AM:
-----------------------------------------------------------------

Thank you.

On the machine I'd like to test it on, I don't have git and cannot install it.  I have tested
it on another machine.  However, I don't think that your test is a valid duplicate of my use
case.

My use case involves a custom assembly descriptor with filesets.  It includes a jar built
with maven and also some text format configuration files and it is these where I need timestamps
preserved.  My situation doesn't use git, it uses svn with the use-commit-times config option
to preserve the timestamps on checkout.  I want these timestamps preserved in the .tar.gz
archive.  I assume that git would have a similar configuration option, but I've not used git
before now.  A valid test case using git would enable this option.  In your test case I see
no timestamps earlier than the time I began the build, but with such an option enabled, presumably,
we would have a valid test of my scenario.

Also I've looked into the plugin source code and I find nothing there that would cause the
source file timestamps to be applied to the destination archive entries, although it's certainly
possible that I've missed where this happens.

I may not respond as promptly as you'd like to your input on this issue because I cannot get
the jira to respect my setting of wanting notification emails on my bugs, and several requests
for help on this have gone unanswered.

                
      was (Author: scohen@javactivity.org):
    Thank you.

On the machine I'd like to test it on, I don't have git and cannot install it.  I have tested
it on another machine.  However, I don't think that your test is a valid duplicate of my use
case.

My use case involves a custom assembly descriptor with filesets.  It includes a jar built
with maven and also some text format configuration files and it is these where I need timestamps
preserved.  My situation doesn't use git, it uses svn with the use-commit-times config option
to preserve the timestamps on checkout.  I want these timestamps preserved in the .tar.gz
archive.  I assume that git would have a similar configuration option, but I've not used git.
 A valid test case using git would enable this option.  In your test case I see no timestamps
earlier than the time I began the build, but with such an option enabled, presumably, we would
have a valid test of my scenario.

Also I've looked into the plugin source code and I find nothing there that would cause the
source file timestamps to be applied to the destination archive entries, although it's certainly
possible that I've missed where this happens.

I may not respond as promptly as you'd like to your input on this issue because I cannot get
the jira to respect my setting of wanting notification emails on my bugs, and several requests
for help on this have gone unanswered.

                  
> 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

Mime
View raw message