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.
NB5.0 + cnd cluster build 060302 installed from linux installer (previously I had an older build installed and correctly uninstalled here). Build fails w/ IOException because cnd1/bin/stdouterr.sh is not executable.
Created attachment 29080 [details] stack trace
Raising to P1. If stdouterr.sh isn't executable then you can't build a project. Thats P1 to me! This needs to be fixed before Milestone 2 can be released.
I know what is going on: stdouterr.sh was added to the release/bin folder with execution flags but NB (or cvs) somehow ignores this mode and the file ends up in cnd1/bin without execution flags. To work around this I added a hack in the code to set execution flags the first time it is executed: ./api/execution/NativeExecution.java: Runtime.getRuntime().exec("/bin/chmod +x " + stdOutErrFile.getPath()); // NOI18N This does work most of the time but there must be a race condition so it tries to execute the file before the chmod command finishes. You will only see this error *one* time. If you try to build again, it works fine. I doubt this is a P1 issue. Possible fixes: 1) figure out why execution flags are dropped 2) set execution flag using a different method, or in a different way 3) wait until the chmod command finishes. Remember, this is done only once.
I do not think we need to set this from runtime. It should be enough to set this flag during build time. At least this what nbbuild/build.xml#build-nozip does to make sure that bin/netbeans is executable and it seems to work sufficiently.
I aggree. We could possibly do something similar.
Fixed in build scripts. I also removed the runtime chmod in NativeExecution.java.
Verified with NetBeans6.0 + cnd cluster.