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: |
Module system redesign (emulators + clean up) |
| Product: |
platform
|
Reporter: |
Jaroslav Tulach <jtulach> |
| Component: |
Module System | Assignee: |
Jesse Glick <jglick> |
| Status: |
RESOLVED
FIXED
|
|
|
| Severity: |
blocker
|
CC: |
jglick
|
| Priority: |
P3
|
Keywords: |
UMBRELLA |
| Version: |
3.x | |
|
| Hardware: |
All | |
|
| OS: |
All | |
|
|
Issue Type:
|
TASK
|
Exception Reporter:
|
|
|---|
| Bug Depends on: |
16328, 26126, 26208, 26211, 26213, 26214, 26219
|
|
|
| Bug Blocks: |
|
|
|
Jesse wrote: - Jarda will move classloaders to boot.jar as part of separation project - I will later move Module, ModuleManager, Events, Installer, *Exception, Util from org.netbeans.core.modules to some lib/modulesys.jar, e.g. org.netbeans.[as]pi.modules; this will depend on openide-util, openide-lookup, openide-modules - remainder of org.netbeans.core.modules will stay where it is in core.jar - Ales/I will move org.netbeans.core.ui.Module{Bean,Node} to autoupdate.jar - org.netbeans.core.{ModuleUpdates,ModuleNode} are deprecated and will be deleted - setup wizard panel for modules will disappear (needs nbui confirmation) - AU's UI for modules may be improved: e.g. one menu item to see ModuleNode, get download wizard, etc. in one place - /nnn major release versions to be semi-deprecated, where bridges are possible; use new code name bases - we encourage API=autoload/GUI=nonautoload separation in module groups with some APIs - AU can use org.netbeans.api.modules for managing installed modules, downloading new ones, etc. - apisupport will use new API for reinstalling modules - I will think about ModuleHistory, decide whether to include in API (probably not, but what to replace it with...) - AU will implement update_tracking.xml-based deletion of unused NBM files after upgrade (already filed?) - I will think about event firing model in module sys (#16328) - I will check on technical problems when changing a module to be autoload in an NBM update Anything else we talked about? Suggestion: Ales you can file tasks for all this (incl. one master tracking task mentioned in core/www/plans/plan.xml for 4.0) and I will send a summary of the plan to nbdev. Sounds OK?