Hi
Well fair enough, it is recognizable as the exit value will in that case
be Integer.MAX_VALUE, so that should not be an issue. (So far for the
non-hardcoded values)
Thanks, Martijn
Stefan Bodewig wrote:
On Wed, 17 Sep 2003, Martijn Kruithof <[EMAIL PROTECTED]>
wrote:
regarding option 1 would
On Wed, 17 Sep 2003, Martijn Kruithof <[EMAIL PROTECTED]>
wrote:
> regarding option 1 wouldn't this still need a patch to set
> killedProcess() to true
Hmm, only if it has been the watchdog that has killed the process
IMHO. If the InterruptedException has been raised for any other
reason, we sho
TCH===
-Ursprungliche Nachricht-
Von: Stefan Bodewig [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 17. September 2003 10:38
An: [EMAIL PROTECTED]
Betreff: Execute#getExitCode doesn't work as advertised
Martijn Kruithof raised this issue in his patch for PR 23150.
The javadocs say
What you say makes sense Stefan,
Antoine
-Ursprungliche Nachricht-
Von: Stefan Bodewig [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 17. September 2003 10:38
An: [EMAIL PROTECTED]
Betreff: Execute#getExitCode doesn't work as advertised
Martijn Kruithof raised this issue in his patc
Martijn Kruithof raised this issue in his patch for PR 23150.
The javadocs say
* @return the exit value, 1 if the process was killed,
but in fact, it doesn't do anything special for a killed process.
Rather than "fixing" this method, I'd like to remove the comment.
For two reasons
(1) Ex
