[
https://issues.apache.org/jira/browse/MASSEMBLY-667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MASSEMBLY-667.
------------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> Allow a <directoryMode> to be applied to the base directory of a tar.gz
> archive
> -------------------------------------------------------------------------------
>
> Key: MASSEMBLY-667
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-667
> Project: Maven Assembly Plugin
> Issue Type: New Feature
> Components: component descriptor
> Affects Versions: 2.4
> Environment: RHEL 5
> Reporter: Steve Cohen
> Priority: Minor
>
> I'm working in a very specialized legacy environment in which it would be
> nice to have an archive (.tar.gz) that had all the permissions as I want from
> the start. Granted it's not all that hard to do after unpackaging with chmod
> running under find, but it would be nice if the base-directory itself had a
> <directory-mode> as do the <filesets> that get packaged under it.
> Bottom-line: the plugin doesn't give me the same level of control as the OS
> does. Archiver support for <fileMode> and <directoryMode> is to that extent
> incomplete.
> The archiver does not create an entry in the archive for the base-directory.
> This is because no matter where you put the <directoryMode> it applies to
> directories WITHIN that <fileset>, not to the root of the fileset itself. If
> a directory entry is not created in the archive, then the -p switch of tar
> will have nothing to "preserve" and just use the default permission for the
> base directory.
> Really, I think to make this work, one would have to be somehow be able to
> put a <directoryMode> on <base-directory> as well as actually create an entry
> in the archive for the base directory.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)