[
http://jira.codehaus.org/browse/MEXEC-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=212325#action_212325
]
Vlad Skarzhevskyy commented on MEXEC-6:
---------------------------------------
We do need killAfter for very different reasons.
We run maven build in cruisecontrol.
In my build I use exec-maven-plugin to run 3-rd party applications.
For example com.google.appengine.tools.admin.AppCfg to deploy war on Google
App engine.
So I set <killAfter>1200000</killAfter> for 20 minutes and if 3-rd party
deployment tools hangs (and it like to do so every now and then) the build
will just fail and I don't need to go ssh to build server and kill haning java
app myself.
> exec:java should wait until spawned non-daemon threads finish
> -------------------------------------------------------------
>
> Key: MEXEC-6
> URL: http://jira.codehaus.org/browse/MEXEC-6
> Project: Maven 2.x Exec Plugin
> Issue Type: Improvement
> Affects Versions: 1.0.1
> Environment: jdk 1.4
> Reporter: David Smiley
> Assignee: Jerome Lacoste
> Fix For: 1.1-beta-1
>
> Attachments: mexec-6.diff
>
>
> exec:java currently only waits until main finishes and then the vm haults
> soon thereafter. If my java executable spawns daemon threads, then your code
> is fine. But if it spawns non-daemon threads, you should be smart enough to
> not quit since there are non-daemon threads still running.
> It's too bad ThreadGroup doesn't have a join since implementing this support
> would be easier if it did.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
