See: Description
| Package | Description |
|---|---|
| org.openide.execution |
NetBeans uses a small interface to describe the execution
of Java-based classes together with arguments.
|
NbClassLoader(FileObject[], ...) does not throw FileStateInvalidException
NbClassLoader(FileObject[], ClassLoader, InputOutput) does not throw FileStateInvalidException any more.
If your module depends on org.openide.execution > 1.9 or higher
there is no need to specify that it also requires an implementation of
the API by use of OpenIDE-Module-Requires: org.openide.execution.ExecutionEngine,
this token will be requested automatically by the org.openide.execution
module itself.
Startup folder removed
Previously it was possible to place objects with an
ExecCookie into the Startup folder
of the system filesystem, and they would be run during
startup.
In NetBeans 4.0 there is no such cookie any more, and that
old style of execution is no longer supported. Modules may
continue to use ModuleInstall.restored for
startup hooks, possibly providing special modes for user
customization, but there is no generic infrastructure for
this.
NbClassLoader constructors deprecated
All of the existing constructors of
NbClassLoader were deprecated since they used
Filesystems to refer to the classpath; one new classpath-safe
constructor was added instead.
For similar reasons, a number of static methods in the class were deprecated as well.
As part of the NetBeans 4.0 build system, the Execution API was split into two halves. The first half continues to be used as before. The second half is now deprecated and lives in a separate module.
|
|
Read more about the implementation in the answers to architecture questions.