Author Topic: extractAll should honor file permissions  (Read 3580 times)

jkatnik

  • Newbie
  • *
  • Posts: 1
    • View Profile
extractAll should honor file permissions
« on: December 29, 2013, 12:58:40 AM »
Hi

I'm creating my app bundle with maven-assembly-plugin, I set permissions with <fileMode>0700</fileMode>
If I extract zip file manually on Debian (UnZip 6.00 of 20 April 2009, by Info-ZIP.  Maintained by C. Spieler.) the permissions are ok however if I extract zip programatically with zip4j the permissions are not applied.

It would be great if ZipFile.extractAll(path) could honour file permissions.

Thanks,
  Jarek

TheNostalgiaIsGoOn

  • Newbie
  • *
  • Posts: 2
    • View Profile
Re: extractAll should honor file permissions
« Reply #1 on: November 10, 2014, 07:01:39 AM »
I hope you enjoy the time you spend here, and find the learning resources useful!

sabrmart

  • Newbie
  • *
  • Posts: 2
    • View Profile
Re: extractAll should honor file permissions
« Reply #2 on: November 27, 2014, 09:12:40 AM »
We are very pleased to have come into the web of it.

 


Warning: Cannot modify header information - headers already sent in /home/content/66/5374066/html/zip4j/forum/Sources/Errors.php on line 346

Warning: Cannot modify header information - headers already sent in /home/content/66/5374066/html/zip4j/forum/Sources/Errors.php on line 347

Warning: Cannot modify header information - headers already sent in /home/content/66/5374066/html/zip4j/forum/Sources/Errors.php on line 348

Warning: Cannot modify header information - headers already sent in /home/content/66/5374066/html/zip4j/forum/Sources/Errors.php on line 351

Warning: Cannot modify header information - headers already sent in /home/content/66/5374066/html/zip4j/forum/Sources/Errors.php on line 352

Warning: Cannot modify header information - headers already sent in /home/content/66/5374066/html/zip4j/forum/Sources/Errors.php on line 353
Connection Problems

Connection Problems

Sorry, SMF was unable to connect to the database. This may be caused by the server being busy. Please try again later.