intermittent pb starting gump from ant ...

[Vincent Massol <vm...@octo.com>]

Hi all,

I am starting Gump with an Ant script on a linux platform. This means
that I am using an Ant exec task to run gen.sh and then to call the
generated update.sh and build.sh

For some reason, it works most of the time and fails from time to time
with an exit code of 143. I seem to remember Sam's issue with Ant and
classpaths that had to be present for paths that were generated by the
Ant build process. Is there any link ?

Do you know why this happens ? Do you think it is linked to the fact
that build.sh is generated by gen.sh ?

I have been running this Ant script for several months on a windows
plastform with no problem and I just discovered this issue when moving
our build machine to a linux platform ...

Thanks for any tip
-Vincent


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

RE: intermittent pb starting gump from ant ...

[Vincent Massol <vm...@octo.com>]

Thanks Stefan,

(sorry for my late answer - I had read your email but simply forgot to
answer ...)

I still haven't fixed my problem but is appearing less frequently. I'm
not sure if it is related to Gump/Ant at all. I'll continue my
investigations.

Thanks again
-Vincent

> -----Original Message-----
> From: Stefan Bodewig [mailto:bodewig@apache.org]
> Sent: 05 July 2002 07:58
> To: alexandria-dev@jakarta.apache.org
> Subject: Re: intermittent pb starting gump from ant ...
> 
> On Wed, 3 Jul 2002, Vincent Massol <vm...@octo.com> wrote:
> 
> > I am starting Gump with an Ant script on a linux platform. This
> > means that I am using an Ant exec task to run gen.sh and then to
> > call the generated update.sh and build.sh
> 
> I've tried to find out what exit code 143 could mean, but couldn't see
> anything.  Take a look at Gump's build.xml - you will need Xalan2 -
> and use the scripts target, that should do the trick.
> 
> > I seem to remember Sam's issue with Ant and classpaths that had to
> > be present for paths that were generated by the Ant build
> > process. Is there any link ?
> 
> I'm not aware of them.
> 
> What I can tell you is that I run build.sh with a completely empty
> CLASSPATH and that I have to do that in order to get the real build
> results (otherwise the jar in CLASSPATH would take precedence over the
> freshly generated ones).
> 
> If you want to do the same from Ant - i.e. start with an empty
> CLASSPATH, you should probably do something like
> 
> <exec ...>
>   <env key="CLASSPATH" value="" />
> </exec>
> 
> when running build.sh.  Or better
> 
> <property environment="env"/>
> <exec newenvironment="true" ...>
>   <env key="PATH" path="${env.PATH}" />
> </exec>
> 
> to use a mostly clean environment.
> 
> Stefan
> 
> --
> To unsubscribe, e-mail:   <mailto:alexandria-dev-
> unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:alexandria-dev-
> help@jakarta.apache.org>



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: intermittent pb starting gump from ant ...

[Stefan Bodewig <bo...@apache.org>]

On Wed, 3 Jul 2002, Vincent Massol <vm...@octo.com> wrote:

> I am starting Gump with an Ant script on a linux platform. This
> means that I am using an Ant exec task to run gen.sh and then to
> call the generated update.sh and build.sh

I've tried to find out what exit code 143 could mean, but couldn't see
anything.  Take a look at Gump's build.xml - you will need Xalan2 -
and use the scripts target, that should do the trick.

> I seem to remember Sam's issue with Ant and classpaths that had to
> be present for paths that were generated by the Ant build
> process. Is there any link ?

I'm not aware of them.

What I can tell you is that I run build.sh with a completely empty
CLASSPATH and that I have to do that in order to get the real build
results (otherwise the jar in CLASSPATH would take precedence over the
freshly generated ones).

If you want to do the same from Ant - i.e. start with an empty
CLASSPATH, you should probably do something like

<exec ...>
  <env key="CLASSPATH" value="" />
</exec>

when running build.sh.  Or better

<property environment="env"/>
<exec newenvironment="true" ...>
  <env key="PATH" path="${env.PATH}" />
</exec>

to use a mostly clean environment.

Stefan

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>