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.

Bug 64634 - java.lang.NoSuchMethodException: java.io.File.setReadable(boolean, boolean)
Summary: java.lang.NoSuchMethodException: java.io.File.setReadable(boolean, boolean)
Status: VERIFIED WONTFIX
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Jaroslav Tulach
URL:
Keywords: JDK_SPECIFIC
Depends on:
Blocks:
 
Reported: 2005-09-19 09:46 UTC by Tomas Danek
Modified: 2008-12-22 18:03 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tomas Danek 2005-09-19 09:46:18 UTC 
This exception appears after just after creating standalone module by project
wizard. Anyway,I cannot realize how this affects usability.
Output from output window:

...
run:
Created dir: C:\Pr\module4\build\testuserdir\etc
run:
java.lang.NoSuchMethodException: java.io.File.setReadable(boolean, boolean)
        at java.lang.Class.getMethod(Class.java:1591)
        at org.netbeans.CLIHandler.secureAccess(CLIHandler.java:663)
        at org.netbeans.CLIHandler.initialize(CLIHandler.java:443)
        at org.netbeans.CLIHandler.initialize(CLIHandler.java:281)
        at org.netbeans.Main.execute(Main.java:157)
        at org.netbeans.Main.main(Main.java:39)
-------------------------------------------------------------------------------
>Log Session: Monday, September 19, 2005 10:38:57 AM CEST
>System Info: 
  Product Version       = NetBeans IDE Dev (Build 200509181800)
  Operating System      = Windows XP version 5.1 running on x86
  Java; VM; Vendor      = 1.6.0-ea; Java HotSpot(TM) Client VM 1.6.0-ea-b42; Sun
Microsystems Inc.
...
Comment 1 Jaroslav Tulach 2005-09-19 12:05:49 UTC 
1. Exception is harmless, I guess.  
2. Fix is simple - upgrade to newer version of JDK, Build 1.6.0-ea-b51 is ok
Comment 2 Tomas Danek 2005-09-20 12:45:33 UTC 
ok. verified.