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 17718 - IllegalArgumentException when disabling a module
Summary: IllegalArgumentException when disabling a module
Status: CLOSED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: Other Linux
: P3 blocker (vote)
Assignee: Vitezslav Stejskal
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-11-15 17:39 UTC by Svata Dedic
Modified: 2008-12-22 20:39 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Exception stacktrace (1.22 KB, text/plain)
2001-11-15 17:40 UTC, Svata Dedic
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Svata Dedic 2001-11-15 17:39:40 UTC
When I'm disabling Javadoc module, which is installed from outside the regular 
modules dir in "reloadable" mode, I'm often getting the attached exception. 
Please note that Javadoc adds a tab to the system Explorer window through its 
module layer.
Comment 1 Svata Dedic 2001-11-15 17:40:43 UTC
Created attachment 3431 [details]
Exception stacktrace
Comment 2 _ ttran 2001-11-15 17:52:30 UTC
a wild guess: security policy does not allow IO permissions to code
outside of {netbeans.home} and {netbeans.user}
Comment 3 Svata Dedic 2001-11-15 17:57:24 UTC
Good try, but this is in my ide.policy file:

grant {
   permission java.security.AllPermission;
};

Comment 4 Jesse Glick 2001-11-15 22:31:10 UTC
Looks like a filesystems problem? I think I have seen this myself, but
I am not sure.
Comment 5 Jan Zajicek 2001-11-19 13:40:00 UTC
Trying pass to Vita.
Comment 6 Jan Chalupa 2001-11-27 11:52:41 UTC
Target milestone -> 3.3.1.
Comment 7 Jan Chalupa 2001-11-27 11:56:22 UTC
Target milestone -> 3.3.1.
Comment 8 Vitezslav Stejskal 2002-01-04 13:27:54 UTC
I tried this scenario and no exception was thrown, javadoc tab was 
added and removed correctly. I think this was problem in Window system 
which was already resolved.
Comment 9 Jan Zajicek 2002-01-07 14:42:01 UTC
Svato, can you verify or reopen this one? Thanks.
Comment 10 Svata Dedic 2002-01-08 08:16:35 UTC
OK, the exception no more appears
Comment 11 Quality Engineering 2003-07-01 16:37:14 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.