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.

Bug 8214 - Hyperlinking enhancements for Ant builds
Summary: Hyperlinking enhancements for Ant builds
Status: CLOSED FIXED
Alias: None
Product: projects
Classification: Unclassified
Component: Ant (show other bugs)
Version: 3.x
Hardware: PC Linux
: P4 normal (vote)
Assignee: issues@projects
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-11-06 19:28 UTC by Jesse Glick
Modified: 2003-06-30 14:47 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2000-11-06 19:28:17 UTC
There are several areas where the hyperlinking from Ant output could be
improved:

- support for column numbers, where available

- support for Jikes compiler

- proper highlighting of the linked-to line in case of errors, and clearing this
highlighting when a new build is done

- highlighting of errors and warnings from Javadoc (these are just class names
and method names, not full file names)

- highlighting of warnings logged from Ant tasks, jumping to the corresponding
place in the build script (using a custom BuildLogger, I guess)
Comment 1 Jesse Glick 2000-11-09 17:34:59 UTC
*** Bug 8193 has been marked as a duplicate of this bug. ***
Comment 2 Jesse Glick 2000-12-24 22:16:59 UTC
Re. Jikes output: (1) build.compiler.emacs must be set to true. In the trunk
this is now done by default in the user-configurable global properties. (2)
Jikes will not provide the full file path for classes in the default package,
for some reason. Probably this is a Jikes bug. For files in a package the output
appears to be correct, and the hyperlinking works. So consider this point
resolved.
Comment 3 Jesse Glick 2000-12-25 02:21:59 UTC
Support for column numbers and standard-UI highlighting of erroneous lines added
in the trunk. Confirmed Jikes output is hyperlinked, too.

Warnings from Javadoc are probably too difficult to parse; better to suggest
that Javadoc itself give proper output.

Highlighting of general warnings from Ant tasks does not seem possible. For
example, if a task just prints some warning (that we would like to link to the
build script), how is that to be distinguished from a random line output by
<javac> (which should be linked to the source file or nothing at all)?
Comment 4 Milan Kubec 2001-06-27 11:36:24 UTC
Verified.
Comment 5 Quality Engineering 2003-06-30 14:47:17 UTC
Resolved for 3.3.x or earlier, no new info since then -> closing.