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: | Why there is ModuleInstall? | ||
---|---|---|---|
Product: | obsolete | Reporter: | Jaroslav Tulach <jtulach> |
Component: | vcscore | Assignee: | Martin Entlicher <mentlicher> |
Status: | CLOSED FIXED | ||
Severity: | blocker | Keywords: | PERFORMANCE |
Priority: | P1 | ||
Version: | 3.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 21676 |
Description
Jaroslav Tulach
2002-03-29 14:48:42 UTC
Reassigning ... The module installs are probably a relict from the past. Starting to work on it... org.netbeans.modules.vcscore.VcsCoreModuleInstall removed, references to Debug class removed. org.netbeans.modules.vcs.advanced.CommandLineVcsModule is there to assure, that all changed FS properties will be written before the IDE exits. This way was suggested by someone. If this is not the correct approach, please reopen and describe an alternate approach. Thanks. I believe Yarda will reopen the issue, if the used solution does not satisfy him ... :-) Verified that all has been fixed except the CommandLineVcsModule. I believe that one can now ensure that the IDE will not exit by holding a FileLock to some file in system file system. So if you know that you should rewrite the filesystem configuration file, hold a lock and the IDE will not finish. O.K., I'll try to use the FileLock. Starting to work on it... Fixed via holding FileLock in dev build Apr 16. ModuleInstall class removed. Okay, verified in development build #200205090100 of NetBeans 3.4. Resolved for 3.4.x or earlier, no new info since then -> closing. |