You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Laurens Blankers (JIRA)" <ji...@codehaus.org> on 2010/08/24 15:46:32 UTC
[jira] Updated: (MASSEMBLY-495) Assembly changes timestamps when
extracting dependency sets
[ http://jira.codehaus.org/browse/MASSEMBLY-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Laurens Blankers updated MASSEMBLY-495:
---------------------------------------
Attachment: MASSEMBLY-495.zip
Minimal demo project demonstrating bug. Extract and run 'mvn install' then check file timestamps in target/demo-1.0-dist/demo-1.0.
> Assembly changes timestamps when extracting dependency sets
> -----------------------------------------------------------
>
> Key: MASSEMBLY-495
> URL: http://jira.codehaus.org/browse/MASSEMBLY-495
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-5
> Reporter: Laurens Blankers
> Attachments: MASSEMBLY-495.zip
>
>
> When creating an assembly containing dependency sets the timestamp of the extraced file is set to the current time in stead of keeping the timestamp from the jar archive.
> Steps to reproduce:
> 1. Create any assembly with a dependency set
> 2. Run
> Expected results:
> The files are extracted from the archive(s) while maintaining their creation/modification timestamps
> Actual results:
> Both creation and modification timestamps are set to current time.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira