[
https://issues.apache.org/jira/browse/MDEP-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16059843#comment-16059843
]
Tim Gokcen commented on MDEP-572:
---------------------------------
After some further experimentation, I can confirm that the tar behaviour is
still broken in 2.9 but is fixed in release 2.10. I'm guessing it may have had
to do with the plexus-archiver upgrade that was included with that release?
> Truncated filenames extracting tar files.
> -----------------------------------------
>
> Key: MDEP-572
> URL: https://issues.apache.org/jira/browse/MDEP-572
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: unpack
> Affects Versions: 2.8, 2.9
> Reporter: Tim Gokcen
> Fix For: 2.10
>
>
> The {{unpack}} goal doesn't handle POSIX.1-2001 long filenames in tar files,
> silently truncating file paths to 100 characters. Tarballs that work just
> fine with BSD or GNU tar has its filenames truncated by the unpack step
> (without any kind of warning or error).
> In my particular example, the Tarball was created by the Apache Maven
> Assembly Plugin using {{<tarLongFileMode>posix</tarLongFileMode>}}.
> As a work-around, I'm using the org.codehaus.mojo Exec-Maven-Plugin in order
> to manually execute tar.
> (Aside: another suggested solution, e.g., on [this StackOverflow question
> about the
> issue|https://stackoverflow.com/questions/26024732/maven-dependency-plugin-unpack-dependencies-cant-support-tar-containing-paths-o]
> is to use the Antrun plugin and execute the {{<untar>}} task, but the
> annoying thing about that is that Ant doesn't respect file permissions when
> extracting tar archives)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
