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 2005/01/04 21:23:24 UTC

DO NOT REPLY [Bug 32941] New: - [PATCH] ExecuteJava should not catch ThreadDeath

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

http://issues.apache.org/bugzilla/show_bug.cgi?id=32941

           Summary: [PATCH] ExecuteJava should not catch ThreadDeath
           Product: Ant
           Version: 1.7Alpha (nightly)
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Core tasks
        AssignedTo: jglick@netbeans.org
        ReportedBy: jglick@netbeans.org
                CC: dev@ant.apache.org


Generally ThreadDeath should be passed through all catch statements, so that the
thread can terminate cleanly; not simply reported, or wrapped in another
exception. Of course finally blocks can and should still run to do necessary
cleanup.

I observed one case where a forked Java process was being run (from the NetBeans
IDE), and sending Thread.stop() (to forcibly halt the build process) resulted in
a BuildException being reported, which is not desirable.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

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