incubator-s4-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthieu Morel (JIRA)" <>
Subject [jira] [Commented] (S4-78) Gradle tasks don't finish as soon as possible
Date Thu, 12 Jul 2012 08:01:37 GMT


Matthieu Morel commented on S4-78:

The relevant gradle issue is and it's already
been delayed quite a few times. 

So I am in favor of adopting your workaround, until the issue is fixed in a gradle release,
and because you have good selling arguments!
> Gradle tasks don't finish as soon as possible
> ---------------------------------------------
>                 Key: S4-78
>                 URL:
>             Project: Apache S4
>          Issue Type: Improvement
>    Affects Versions: 0.5
>            Reporter: Daniel Gómez Ferro
>             Fix For: 0.5
>         Attachments: 0001-Explicit-shutdown.patch
> Some Gradle tasks don't finish as soon as possible, since they leave a non-daemon thread
running. It seems that after a timeout (1 minute) the thread exits and the task completes.
> This is specially apparent after the improvements in build time in S4-72
> One possible workaround is to explicitly shutdown the JVM after the task is finished.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message