maven-issues mailing list archives

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


Steve Cohen commented on MASSEMBLY-670:

Thank you.

I had an idea as to what the plugin might not have liked.  My assembly descriptor was defining
both input and output directories of fileSets using properties that were defined in pom.xml.
 My theory was that this could have been a phase timing issue.  Since eventually that correct
directories were being made, maybe the problem was that while the filesets were being read,
the properties had not been interpolated.  That was what the "[DEBUG] After assembly is interpolated:"
logging message showed.  

That was my theory.  Alas, it did not pan out.  I replaced all these property references with
hardcoded directory names.  It didn't help.  The same error message was produced and the timestamps
were still not what I was expecting.
> assembly plugin tar.gz format does not preserve timestamps of files it adds to archive
> --------------------------------------------------------------------------------------
>                 Key: MASSEMBLY-670
>                 URL:
>             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:

View raw message