ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 20062] New: - Create flag to control System.exit() call in org.apache.tools.ant.Main
Date Tue, 20 May 2003 14:41:19 GMT
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=20062>.
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=20062

Create flag to control System.exit() call in org.apache.tools.ant.Main

           Summary: Create flag to control System.exit() call in
                    org.apache.tools.ant.Main
           Product: Ant
           Version: 1.5.3
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Minor
          Priority: Other
         Component: Core
        AssignedTo: dev@ant.apache.org
        ReportedBy: dpociu@itgp.com


As ant tasks are called from Java classes, it would be extremelly helpful to be 
able to control whether System.exit() is called or not at the end of the tasks.

Currently, the workaround is to replace the security manager with something 
like org.apache.tools.ant.util.optional.NoExitSecurityManager. This tends to be 
messy, since the exception stacktrace gets printed no matter what, and 
therefore the ant output cannot easily displayed to a user.

Perhaps a top-level attribute in the ant XML could specify whether System.exit
() should be called or not.

Mime
View raw message