RE: Unwanted behavior - fixcrlf changes files to un-executable

2006-08-15 Thread Brown, Carlton
How do you believe policy files could be applied to resolve this problem? -Original Message- From: Martin Gainty [mailto:[EMAIL PROTECTED] Sent: Monday, August 14, 2006 6:28 PM To: Ant Users List Subject: Re: Unwanted behavior - fixcrlf changes files to un-executable You can govern who

Re: Unwanted behavior - fixcrlf changes files to un-executable

2006-08-14 Thread Martin Gainty
You can govern who touches what, what is touched and more specifically how Java Processes touches directories via the policy files But then again you already knew that right? Viel Gluck * This email message and any files transmit

Re: Unwanted behavior - fixcrlf changes files to un-executable

2006-08-14 Thread Alexey N. Solofnenko
Usually when a file is overwritten, its permissions are not changed. Executable permission can be lost when the file first deleted, then created again. Carlton, if you have a special file extension or folder, you can run task after newlines are fixed. - Alexey. Dominique Devienne wrote: I'm a

Re: Unwanted behavior - fixcrlf changes files to un-executable

2006-08-14 Thread Alexey N. Solofnenko
Usually when a file is overwritten, its permissions are not changed. Executable permission can be lost when the file first deleted, then created again. Carlton, if you have a special file extension or folder, you can run task after newlines are fixed. - Alexey. Dominique Devienne wrote: I

RE: Unwanted behavior - fixcrlf changes files to un-executable

2006-08-14 Thread Brown, Carlton
Users List Subject: Re: Unwanted behavior - fixcrlf changes files to un-executable I'm afraid there's no fix, as Java is not permission-aware. probably creates a new file when it does something, and there's no way in Java to preserve the permissions. You could 'fix' the per

Re: Unwanted behavior - fixcrlf changes files to un-executable

2006-08-14 Thread Dominique Devienne
I'm afraid there's no fix, as Java is not permission-aware. probably creates a new file when it does something, and there's no way in Java to preserve the permissions. You could 'fix' the permissions after the fact, using which simply forks to the command line chmod executable, assuming you know