[
https://jira.codehaus.org/browse/MASSEMBLY-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=335270#comment-335270
]
Steve Cohen edited comment on MASSEMBLY-670 at 11/6/13 6:33 AM:
----------------------------------------------------------------
As for Eclipse, I had to make the assembly plugin a dependency. Then I could
see all the jars that it required. I selected them all and did the get source,
but the plexus stuff did not come over, altho the maven sources did. Is it
hosted at a repository different from maven central perhaps?
As for git, would that pull over the latest source? Is that what I want, or do
I want the source that the plugin is using?
Anyway, all of this is moot now that I've identified <lineEnding> as the
culprit. Stepping through in the debugger was what led me to that conclusion
although I couldn't actually see the source at that point. You should be able
to replicate the issue simply by putting a <lineEnding> tag in a <fileSet>.
I need the plugin to preserve timestamps there. Even though apply line-endings
is a modification of the source file, it is not a material modification as far
as the logic of my build is concerned and it's important that those timestamps
be preserved.
was (Author: sco...@javactivity.org):
As for Eclipse, I had to make the assembly plugin a dependency. Then I
could see all the jars that it required. I selected them all and did the get
source, but the plexus stuff did not come over, altho the maven sources did.
Is it hosted at a repository different from maven central perhaps?
As for git, would that pull over the latest source? Is that what I want, or do
I want the source that the plugin is using?
Stepping through in the debugger led me to that conclusion although I couldn't
actually see the source at that point. You should be able to replicate the
issue simply by putting a <lineEnding> tag in a <fileSet>.
I need the plugin to preserve timestamps there. Even though apply line-endings
is a modification of the source file, it is not a material modification as far
as the logic of my build is concerned and it's important that those timestamps
be preserved.
> 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
