Community
Participate
Working Groups
The CVS adapter must consider the file permission flags passed on checkout and send the server the file permission flags on commit. Without this support, Unix installs, cannot correctly checkout scripts and executables from Eclipse CVS that need execute permission to run. NOTES: Jean-Michel (9/18/01 9:06:38 AM) This causes problems with Eclipse's build process. They now have to run the checkout from the command line, since it honours the file permissions correctly. JEM (9/19/2001 12:20:30 PM) I don't see any way to set executable permissions on a File in Java. JEM (10/1/2001 11:32:53 AM) I believe Core is adding executable permissions support to their DLL. MichaelV (10/10/2001 9:28:07 AM) Core support is only for maintaining permissions when copying files locally!
PRODUCT VERSION: R1.0
We had this capability but I think it was removed over several refactorings. We'll need to have a look and add it back if it was removed.
File permissions on commit are meaningless unless it is the first commit of an added file and then it is only the execute bit that matters. Since there is no way to get the executable bit in Eclipse, there is no way to know whether to send it or not. There is also no way to set it locally on checked out files. Committing over an already existing file will not change the permissions. Bottom line: If you need to checkout executables as executable, you have to use the command line client.
This is a major bug on UNIX/Linux if you can't have the execute bit set on files in the repository. It's extremely common to have executable scripts (say, build scripts) in the repository, and they need to be executable. Many other IDEs (and the command line client) have this feature. As-is Eclipse just doesn't work for say a GNOME or KDE or Mozilla developer. You say "there is no way to get the execute bit in Eclipse" - but _that's the bug_, right? Just because it's hard to fix doesn't mean it's fixed, or that the bug is invalid. Eclipse is still buggy here, and in a significant way that keeps people from using it on Linux. While yes you can't change the execute bit post-import with CVS, it does need to be checked out correctly once it's imported, and the infrastructure/UI should be planning for future version control systems that aren't quite as braindead as CVS re: file permissions. I believe this bug should be reopened and addressed. If the file abstraction layer or whatever is relevant doesn't support execute bit handling, then it's not portable, and should be fixed.
Reopening
We are hoping to address this bug in 2.1 *** This bug has been marked as a duplicate of 22923 ***
