Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <dev@ant.apache.org>
content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: Sshexec fail on starting a service (websphere)
Date: Fri, 5 Mar 2004 10:12:36 -0800
Message-ID: <200403051812.i25ICKOU016041@barrierb241.nike.com>
Thread-Topic: Sshexec fail on starting a service (websphere)
Thread-Index: AcQCmrNzVRMVg0ofTEWZFe2YMwgw9QAQQDQg
From: "Anderson, Rob (Global Trade)" <Rob.Anderson@nike.com>
To: "Ant Developers List" <dev@ant.apache.org>
Content-Type: text/plain;
 charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

> -----Original Message-----
> From: Steve Loughran [mailto:steve_l@iseran.com]
> Sent: Friday, March 05, 2004 2:11 AM
> To: Ant Developers List
> Subject: Re: Sshexec fail on starting a service (websphere)
>=20
>=20
> Anderson, Rob (Global Trade) wrote:
> > The sshexec task, jsch and ssh cannot be expected to=20
> anylize the output from a command that is run. This is why=20
> there is an exit status. The example of echo is a good one.=20
> Echo will succeed and report exit status 0 to the process=20
> that calls it. If you wish to anylize the output of echo, you=20
> need to do this in the parent process.
>=20
>=20
> While I agree with everything you say, the limited scope of=20
> exit codes=20
> really irritates me.
>=20
> all we have to return errors and success is a number, a=20
> number that can=20
> also be used in different ways by java.exe, and which behaves=20
> differently on different boxes.
>=20
> This code snippet from the LGPL smartfrog tasks=20
> (smartfrog.org) show the=20
> problem. I am forking java, but java.exe can return things if=20
> it feels=20
> like it, so the program we fork knows to return -1 for an error -the=20
> switch statement should say 0=3D=3Dgood, -1 error, else: trouble.
>=20
> Only java1.4.2 on hpux seems to return 255 instead of -1 on=20
> exec. I can=20
> see a bit of platform specific details creeping in there, and=20
> it makes=20
> me unhappy.
>=20
>          switch(err) {
>              case 0:
>                  return;
>                  //-1 is an expected error, but
>                  //for some reason smartfrog on HP-UX returns=20
> something=20
> else.
>                  //so we catch 255 as well.
>              case -1:
>              case 255:
>                  throw new BuildException(failureText);
>              default:
>                  throw new BuildException(errorText+" - error=20
> code "+err);
>          }
>=20
>=20
> Can we ever move to a world where executed programs throw a full=20
> exception up to the caller, rather than just return a status code?

The decision to return a status code was probably made before I was =
born. If there were a machine that ran Java as it's OS, rather than a =
java vm on top of solaris/linux/hpux/windows/etc, we could have such an =
environment where exceptions could be thrown to the parent process.

-Rob Anderson

>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>=20
>=20
>=20


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org