You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by bu...@apache.org on 2003/01/20 13:53:20 UTC

DO NOT REPLY [Bug 16255] New: - XmlLogger without DOM tree

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=16255>.
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=16255

XmlLogger without DOM tree

           Summary: XmlLogger without DOM tree
           Product: Ant
           Version: 1.5.1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Other
        AssignedTo: ant-dev@jakarta.apache.org
        ReportedBy: patrick.lisser@canoo.com


In large projects and/or when debug level includes DEBUG (or more) the
DOM tree built up in the XmlLogger grows to an inacceptable size.

It seems as there are two reasons for building a DOM tree at all and
flushing it at the very end of the build:
- consumed time of the build, targets, and tasks is added as an attribute
  to the appropriate element. The same holds for exceptions.
- Concurrent log calls are traced back to where they belong.

The former can be changed by logging the time and exceptions not as attributes 
but as subelements. If necessary the result can easily be converted to the old 
style by applying XSL.
For the latter, unfortunately, I don't have any solution.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>