DO NOT REPLY [Bug 22718] New: - [PATCH] Print info on nested build scripts in

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22718>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22718

[PATCH] Print info on nested build scripts in <ant>

           Summary: [PATCH] Print info on nested build scripts in <ant>
           Product: Ant
           Version: 1.6Alpha (nightly)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Core tasks
        AssignedTo: dev@ant.apache.org
        ReportedBy: jesse.glick@netbeans.com


This patch just lets you see when you are entering or exiting a nested build
script with the <ant> task. For a build system composed of many nested scripts,
esp. "template" scripts called with <property>s, this can be very helpful for
seeing what is going on.

Make has done this for years.

Perhaps better would be to change/extend the BuildListener interface to
explicitly mark entry & exit points for subprojects, so that the logger impl
could choose to format this information in different ways - e.g. displaying
messages from nested projects using indentation.

(I also tried to patch the default console build logger to autodetect messages
coming from nested projects, using some sort of stack of Project objects gotten
from existing events, but this did not seem like it would be reliable, so I
switched to logging the info directly from <ant>.)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org