|Re: [sbt] Forked builds and System.exit||Kevin Scaldeferri||10/9/12 11:04 AM|
I would also either like SBT to do this, or to provide a mechanism to do it. I recently discovered this issue using the testNG plugin (testNG had a thread leak, now fixed in HEAD but not released) and it was quite frustrating to track down the cause. And, I still haven't sorted out a workaround to terminate the forked process.
On Mon, Oct 8, 2012 at 7:36 PM, James Roper <jro...@gmail.com> wrote:
I'm seeing inconsistent behaviour between forked tasks and the main build. This is a similar, but different situation to in this thread:
|Re: Forked builds and System.exit||phausel||10/9/12 11:35 AM|
|Re: [sbt] Re: Forked builds and System.exit||Kevin Scaldeferri||10/17/12 2:23 PM|
I'm happy to see this was quickly patched on the 0.13 branch, and perhaps it will get backported for 0.12.2, but in the meantime, can anyone suggest a workaround to force my forked tests to exit?