https://bz.apache.org/bugzilla/show_bug.cgi?id=65148
--- Comment #2 from Stefan Bodewig <bode...@apache.org> --- I'm afraid my memory of the introduction is rather blurry as well. Not killing the process has not really been a design goal, we wanted to ensure the process exit code actually reflected whether the build was successful. The Launcher class is supposed to be used as the java process' main class. For an embedded usage of Ant I feel the class is doing to much anyway like spitting diagnostic messages to System streams, modifying system properties or creating custom classloaders. I doubt ideas and other things that run Ant embedded actually use Launcher - more likely they create a Project instance (using ProjectHelper, quite possible a self-provided one) and execute targets on it. Of course we could add yet another command line argument to Launcher that suppressed System.exit. And we can make the documentation more clear this class is not really intended to be used for embedding Ant. The page is about "running Ant" not embedding it, after all :-). -- You are receiving this mail because: You are the assignee for the bug.
