[
https://jira.codehaus.org/browse/MASSEMBLY-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitanjan Sarkar updated MASSEMBLY-343:
--------------------------------------
Attachment: symlink-test.tar.gz
Symlink test project.
Contains a symlink generator (symlinks generated using ant-runer and bundled
using assembly plugin) and a symlink consumer that unwraps the dependency using
(dependency plugin).
My objective is to pack a symlink (using assembly) and unpack it (using
dependency-unpack) and see if links remain intact.
With assembly-plugin v2.4, the links get resolved into a regular folder
structure (dereferenced basically) at the end of the assembly.
With v2.5, atleast the assembly-generated artifact should bundle symlinks. But
instead the symlinks appear as empty directories.
> add symbolic links managment (java7+ only supported)
> ----------------------------------------------------
>
> Key: MASSEMBLY-343
> URL: https://jira.codehaus.org/browse/MASSEMBLY-343
> Project: Maven Assembly Plugin
> Issue Type: Wish
> Affects Versions: 2.2-beta-2
> Environment: linux, ubuntu
> Reporter: Godet Gilles
> Assignee: Kristian Rosenvold
> Fix For: 2.5
>
> Attachments: MASSEMBLY-343_maven-assembly-plugin_fixed.patch,
> MASSEMBLY-343_maven-assembly-plugin.patch, symlink-test.tar.gz
>
>
> i need to buid archives ( tar for example ) with symbolic links
> the plugin build an archive with a file containing the destination of the
> link, not the link itself
> => the plugin need an option to know if deferencement of links is needed
> this is just like -h option of tar
> -h, --dereference
> don't dump symlinks; dump the files they point to
> actually, if you do an archive of /lib, for example, many file will be in
> double with diff̮̩rent names. extract of archive will not be the
> exactly the same as the source of the archive. => this is a test !
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
