This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
When you add a file into CVS that has the execute permission bit set NetBeans is removing that permission (before the file is added?). When you check in a file to CVS (using command line cvs) which has the execute bit set it will be set on the CVS server, on checkout cvs will set the execute permission on the file on top of your normal umask. NetBeans seems to remove this permission before the file gets to CVS so on checkout the permission isn't set, this then needs to be changed on the CVS server. This is what happens when using command line cvs: $ umask 0002 $ touch foo750.sh $ chmod 750 foo750.sh $ ls -l foo750.sh -rwxr-x--- 1 tom tom 0 May 19 17:50 foo750.sh $ cvs add foo750.sh cvs add: use `cvs commit' to add this file permanently $ cvs ci -m "foo" foo750.sh ... initial revision: 1.1 $ rm foo750.sh $ cvs up foo750.sh cvs update: warning: `foo750.sh' was lost U foo750.sh $ ls -l foo_750.sh -rwxrwxr-x 1 tom tom 0 2009-05-19 17:52 foo750.sh When I commit the file using NetBeans and check it out it doesn't have have the execute permissions set: $ ls -l bar750.sh -rw-rw-r-- 1 tom tom 0 2009-05-19 17:54 bar750.sh I don't actually use NetBeans (a text editor does me for my coding needs) but some of my co-workers do and have noticed this on projects we work on together. I've tested this using the following version: Product Version: NetBeans IDE 6.5.1 (Build 200903060201) Java: 1.5.0_16; Java HotSpot(TM) 64-Bit Server VM 1.5.0_16-b02 System: Linux version 2.6.24-23-generic running on amd64; UTF-8; en_GB (nb) Userdir: /home/mark/.netbeans/6.5
I am seeing this behavior without NetBeans ever checking in the file: - I created an executable shell script - I checked it in with command line CVS. - I checked it out with command line CVS - execute permission is set. - I checked it out with NetBeans - execute permission is not set.