the 6.0 M10 - 200706262201 build:
full install on Linux as a root.
While runing as user, the Ruby tries to change file permissions, which is of course impossible.
I see this also as a security issue - user software tries to modify file permissions.
This exception is raised on every startup => P1
java.io.IOException: could not run [/bin/chmod, u+rx, gem, jirb, rake, rdoc, spec, jruby.bat, jirb_swing.bat,
generate_yaml_index.rb, gemri, jruby, rails, gem_mirror, jruby.rb, jrubycli, jrubysrv, spec_translator, gem_server,
gemwhich.bat, gemwhich, gem.bat, gemlock, update_rubygems, jirb_swing, jrubyc, _jrubycleanup.bat, testrb,
gem_server.bat, _jrubysetcp.bat, _jrubyvars.bat, jirb.bat, jrubyd.bat, jrubyw.bat, index_gem_repository.rb,
_jrubyvmopts.bat, gem_mirror.bat] : Exit value=1
[catch] at java.lang.Thread.run(Thread.java:595)
Permissions modifications in module installer are not necessary at the moment when it is guaranteed that jruby binaries
have executable permissions set, no matter where user got the build (installer, hudson, some custom build, ...)
The module is doing a chmod in the ModuleInstall on all the JRuby files because that is the only* way to make JRuby work with Auto Update.
*=Only way I know of, and I did ask around. There was also a similar question on nbdev two days ago where Jesse gave pretty much the same answer.
Gordon Prieur wrote:
>is there any way I can install an nbm with execution bits turned on
>or do I have to do that from my module?
I think you need to use ModuleInstall + InstalledFileLocator.
I would love to be able to annotate these bits with executable permission somehow in the NBM and have the Auto Update client restore this state when the
NBM is installed, rather than doing this each and every time.
One thing I could do now is to just -silently- try chmodding - in other words, catch and swallow any IO exceptions that result.
I'm not sure what the security implications are here.
(Btw this is a duplicate, I should dig up the others and combine them)
I'm silently logging IO exceptions now rather than causing the printstacktrace popup. Reducing priority. Fixing this completely will depend on issue 24357.
IDE: [6/27/07 10:28 AM] Committing started
Checking in src/org/netbeans/api/ruby/platform/RubyInstallation.java;
/cvs/scripting/ruby/platform/src/org/netbeans/api/ruby/platform/RubyInstallation.java,v <-- RubyInstallation.java
new revision: 1.30; previous revision: 1.29
Checking in manifest.mf;
/cvs/scripting/ruby/platform/manifest.mf,v <-- manifest.mf
new revision: 1.22; previous revision: 1.21
IDE: [6/27/07 10:28 AM] Committing finished
*** Issue 107410 has been marked as a duplicate of this issue. ***
*** Issue 104385 has been marked as a duplicate of this issue. ***
Reassigning this issue to newly created 'ruby' component.
I can't fix this until the plugin manager supports file permissions
Nothing else to fix here. We can't do more here.
BTW NetBeans runs JRuby through 'java', so no issue from NetBeans + JRuby.