Java Reference
In-Depth Information
Previous Error/Warning
(
Ctrl+Alt+Up
) navigates to the source of the
previous error shown in the
Messages
window.
■
Next Error/Warning
(
Ctrl+Alt+Down
) navigates to the source of the next
error shown in the
Messages
window.
■
Help
accesses Ant-related help.
■
Toggle tree/text mode
changes the
Messages
view between a structured
tree view and plaintext.
■
Show All Messages
displays all available messages. This can create a very
large list of messages, because it shows every step the Ant process has taken.
Enabling this option can be useful when you're debugging Ant scripts.
■
Expand all
(
Ctrl+NumPad +
) expands the message hierarchy to view all
entries.
■
Collapse all
(
Ctrl+NumPad -
) collapses the message hierarchy to only
show the root targets.
■
Auto scroll to source
, if enabled, loads the source file into the editor at the
source of an error, warning, or message you select in the
Messages
window.
This goes for both compilation messages, which loads source files, and Ant
messages, which loads the build file.
■
Selecting the view mode
Most Ant builds generate a number of results and messages. Even if you don't
encounter any problems, you can still use the Ant
Messages
window to follow the
progress of the build. You have your choice of two different views: a tree view and
a text view. Both show the same data, but in different ways.
In tree mode, the results of the Ant build are displayed as a hierarchy of mes-
sages rooted at the Ant targets that generated them. Each step in the Ant build
process is shown, regardless of whether it produces output or error messages. By
default, targets are expanded only if they have produced meaningful output
(such as a compilation error). You have the option of collapsing or expanding
individual nodes or the whole tree en mass via the toolbar. A typical example of
an Ant build in tree mode is shown in figure 5.10.
In the example shown in figure 5.10, a problem was encountered with the Ant
target
compile
. As you can see, there was an invalid variable name. The source
file reference and compiler error message are shown, along with the location
within the Ant script where the error originated, just as with the built-in com-
piler. Double-clicking either of these messages will take you to the offending
