Instances of this class are looked up in lookup and called one by one to initialize the rest of the system.
Parser and interpreter for automatic module dependencies.
A struct for holding information on the result of dependency refinement.
Handler for core.jar options.
Handler for core options.
Handles the --reload command-line option.
Utility class permitting you to verify that a set of modules could be enabled together.
Interface to environment that the Module system needs around itself.
Ability to locate NBM-installed files.
Main class for NetBeans when run in GUI mode.
The default lookup for the system.
Class representing one specially-treated section in a module's manifest file.
Module section for an Action.
use META-INF/services to register convertors.
use new debugger API
Module section for a Data Loader.
Representation of the history of the module.
Rudimentary manager useful for non-GUI platform applications.
Controller of the IDE's whole module system.
Implementation of Places to deal with command line --cachedir argument.
Utility class to provide localized messages explaining problems that modules had during attempted installation.
Stream handler for internal resource-based URLs.
A class that encapsulates all the splash screen things.
Logger that will enable the logging of important events during the startup annotated with real time and possibly time differences.
Interface for deploying test modules.
Class that sets the java.util.logging.LogManager configuration to log into the right file and put there the right content.
First there is the Open API:
Relevant classes are
ModuleInfo, giving general information
about modules (version, name, etc.) and available through lookup;
ModuleInstall, permitting a module to customize its installation
In this package the remainder of the system is implemented, but this is still broken into pieces to make it easier to work with.
core.modules.Module is the concrete version of
ModuleInfo, with additional
information such as the full manifest contents, the live classloader in
use, and some details of where it came from and its behavioral parameters.
core.modules.ModuleManager is the class responsible for keeping track of the set of
modules and their interdependencies, and ultimately controls which modules
can or cannot be installed and why.
core.modules.ModuleInstaller is the interface used by the manager to physically load
the contents of the module into the IDE.
core.modules.Events permits major events to be logged
asynchronously for subsequent formatting and display.
Private helper classes include
ChangeFirer to fire module manager
Util for module-related utility functions.
MultiURLClassLoader is an optimized classloader used for modules
that is able to handle multiple parents, dynamic parent addition and removal,
and streamlining of the package search algorithm based on features of the Modules API.
Also the exceptions
core.modules.InvalidException are thrown when creating or
working with modules.
This layer is largely independent of the workings of the IDE; it uses some Open APIs but only those which can be used in a standalone context. So it makes sense to test these classes in isolation from the others, and without starting the IDE. It is not permitted to use UI and employs no localized messages. (Exception messages need not be localized; problems likely to be encountered by end users who are not module developers should be handled elsewhere are localized.)
The other layer is more dependent on the rest of the IDE core, and the details of the Modules API.
really implements the loading of modules: registering layers,
registering the existence of help sets, loading the beans forming manifest
sections and making them available, and running
core.modules.ManifestSection is used by
represent one section in a module manifest during installation, and may be used in other
parts of the core (e.g. if sections are registered via lookup for interpretation elsewhere).
core.modules.ModuleList keeps track of the set of installed modules on disk, and is the point
of contact for reading and writing the list of installed modules, any serialized
ModuleInstall instances, and autoscanning the modules folder.
core.modules.ModuleHistory tracks the origin of a module, whether it was installed before
and where, and what version it last was. This information is supplied by
based on its knowledge of the settings on disk, and used by
NbInstaller to invoke
performs NetBeans-specific logging of module system
events, such as displaying friendly messages in the splash screen, status bar, or console.
It can also be a point of contact for performance measurements.
core.modules.ModuleSystem is a high-level controller for the whole
module system. Core initialization classes needing to start some process in the module system,
such as "install newly found modules", should use a method call on this class, which will delegate
the details to other module-system objects.
core.modules.TestModuleDeployer is a service available via lookup
which deploys test modules; accessible separately with a thin API for use by modules
such as the API Support.
AutomaticDependencies is used to parse XML files constrained by module-auto-deps-1_0.dtd
and automatically update dependencies used by old modules as a result. This is very
useful for maintaining backward compatibility across major refactorings.
Also of interest:
core.ui.ModuleBean provides a Swing-safe UI
ModuleManager, used by the Modules node.
Those interested in using the independent parts of the module system as a standalone JAR should run:
ant -f core/build.xml lib-modules
Built on May 24 2013. | Portions Copyright 1997-2013 Oracle. All rights reserved.