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.
Summary: | CNFEs for other module's classes | ||
---|---|---|---|
Product: | obsolete | Reporter: | Svata Dedic <sdedic> |
Component: | languages | Assignee: | issues@ide <issues> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | ||
Priority: | P2 | ||
Version: | 3.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Svata Dedic
2002-02-19 07:34:46 UTC
did you have the sources of other modules mounted? or you expect to have all the Nb modules accessible? btw which engine did you use? beanshell/dynamicjava/jython? I tried to use BeanShell and DynamicJava. I didn't mount the sources, will it help ? From the module's code I thought that it uses BeanShell from modules/ext though the scripting module's classloader, which does not see other modules or the code inside FileSystems. The only scripting language in nb that supports using the FileSystem as a classpath is currently DynamicJava. It builds the classpath dynamically and adds it to the scripting classpath. if we update to beanshell 1.2b4 (maybe earlier, I didn't check), we could add the mounted filesystems to the classpath as well, the current version bundled with Netbeans doesn't allow that.. updated the beanshell support to use the 1.2b5 jar as found on Beanshell's homepage (as discussed with Pat - owner of the Beanshell project - that's the most uptodate stable version) I've added the code that adds the mounted filesystems to the classpath of the beanshell interpreter. I'm not sure it will exactly solve your problem but I don't think it's ok to access the Nb internals from within the scripting module.. the same was the case with the filesystems in the early days and was removed from there some time ago already.. |