Examination and execution of Ant build scripts.
Utilities for examining and running Ant scripts.
Ways of influencing how Ant is run inside NetBeans.
The main uses of the Ant integration module are self-contained and do not interact directly with other modules: the user selects a target in an Ant script and runs it. Nonetheless, there are a few significant ways other modules can interact with this module:
Permits customization of the way Ant output is displayed.
Registering custom Ant task and type definitions (when these can be run inside the NetBeans JVM only). Typically used to add special tasks which somehow script the IDE, such as connecting the JPDA debugger to a process launched by Ant.
Permits additions to the default Ant classpath.
Examining cached and introspected data about which tasks and types are known to be defined in the user's Ant scripts, and what their design-time structure is. Used by XML code completion, for example.
Running named targets in specified Ant scripts. Can be used
by modules which provide a different UI for initiating Ant
ActionUtils provides a more convenient
wrapper around this functionality.
Added ability to get originating script for a
Added ability to get user properties defined for a build.
Added ability to get the underlying
object for advanced formatting.
Added a new convenience class for getting some common information from Ant scripts.
getPropertyNames can now work with Ant references
as well as plain properties. This is critical for loggers which
wish to inspect e.g. the runtime value of a classpath given as:
which otherwise would be inaccessible.
The principal use cases for the API are covered in the overall API architecture.
The sources for the module are in the NetBeans Mercurial repositories.
Read more about the implementation in the answers to architecture questions.
Built on May 16 2013. | Portions Copyright 1997-2013 Oracle. All rights reserved.