I'm facing the same issue (running Bliss on a Synology NAS).
As for the move to Java 7: this would surely make it possible to facilitate setting different default file permissions. I'm not sure though how widely available Java 7 is - I think Synology has just made their own Java package available for users to install this month - I had to install a package from a community source to make it work, so maybe it would be good to look into a way how to make this work with the existing Java 6 version.
As I said in my email:
It might be possible to solve this issue (and do quite a lot of other things) if there was some kind of post-treatment hook that executes a user defined command after Bliss fixes an album. The directory of the treated album could be passed as an argument. That way it would be possible to e.g. chmod/chown the directory back to a predefined permission scheme.
Thanks for looking into this Dan.
I'm facing the same issue (running Bliss on a Synology NAS).
As for the move to Java 7: this would surely make it possible to facilitate setting different default file permissions. I'm not sure though how widely available Java 7 is - I think Synology has just made their own Java package available for users to install this month - I had to install a package from a community source to make it work, so maybe it would be good to look into a way how to make this work with the existing Java 6 version.
As I said in my email:
It might be possible to solve this issue (and do quite a lot of other things) if there was some kind of post-treatment hook that executes a user defined command after Bliss fixes an album. The directory of the treated album could be passed as an argument. That way it would be possible to e.g. chmod/chown the directory back to a predefined permission scheme.