hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Nauroth <cnaur...@hortonworks.com>
Subject Re: [PROPOSAL] introduce Python as build-time and run-time dependency for Hadoop and throughout Hadoop stack
Date Wed, 21 Nov 2012 21:44:37 GMT
Sorry, to clarify my point a little more, Ant does allow you to make
declarations to explicitly set the desired file permissions via the
fileMode attribute of a tarfileset.  However, it does not have the
capability to preserve whatever permissions were naturally created on files
earlier in the build process.  This is a difference in maintainability, as
adding new files to the build may then require extra maintenance of the Ant
directives to apply the desired fileMode.  This is an easy thing to
overlook.  A solution that preserves the natural permissions requires less
maintenance overhead.

I couldn't find a way to make assembly plugin preserve permissions like
this either.  It just has explicit fileMode directives similar to Ant.
 (Let me know if I missed something though.)

To see symlinks show up in distribution tarballs, you need to build with
the native components, like libhadoop.so or bundled Snappy.


On Wed, Nov 21, 2012 at 1:30 PM, Radim Kolar <hsn@filez.com> wrote:

> Dne 21.11.2012 22:03, Chris Nauroth napsal(a):
>  For creation of the distribution tarballs, the Maven
>> Ant Plugin (and actually the underlying Ant tool) cannot preserve file
>> permissions or symlinks.
> maven assembly plugin can deal with file permissions. not sure about
> symlinks. I do not remember dist tar to have symlinks inside.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message