You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by Vincent Massol <vm...@pivolis.com> on 2003/06/06 23:08:58 UTC
[cactus] build failure - need help
Hi,
I need some help to diagnosis why the jakarta-cactus-sample-servlet-12
project is failing to build with Gump. The problem has to do with
starting Tomcat 3.x but the build output is not enough to diagnosis the
problem.
During the build there is a file created:
jakarta-cactus/samples/servlet/target-12/test/test-reports/tomcat3x.out
Would it be possible to have access to this file?
More generally is there a way to a web read access to the area where
Gump builds the projects on Nagoya?
Thanks
-Vincent
Re: [cactus] build failure - need help
Posted by Christopher Lenz <cm...@gmx.de>.
A cleaner and more flexible approach might be to use an Ant XmlLogger,
and then transform the resulting xml log file to multiple html log
files, one for INFO, one for WARN and one for DEBUG (for example).
But, no, I'm not volunteering (yet)
Adam Jack wrote:
> This is another example of why it'd be nice to be able to set debug on in
> the gump descriptor, and have -debug passed to ant. Some build problems can
> be such that they work locally, but fail at the remote site. They need to be
> debugged at the remote site, IMHO.
>
> I've said it before, but I'll submit an enhancement request for it this
> time.
>
> regards
>
> Adam
> -----Original Message-----
> From: Vincent Massol [mailto:vmassol@pivolis.com]
> Sent: Friday, June 06, 2003 3:09 PM
> To: gump@jakarta.apache.org
> Subject: [cactus] build failure - need help
>
>
> Hi,
>
> I need some help to diagnosis why the jakarta-cactus-sample-servlet-12
> project is failing to build with Gump. The problem has to do with
> starting Tomcat 3.x but the build output is not enough to diagnosis the
> problem.
>
> During the build there is a file created:
> jakarta-cactus/samples/servlet/target-12/test/test-reports/tomcat3x.out
>
> Would it be possible to have access to this file?
>
> More generally is there a way to a web read access to the area where
> Gump builds the projects on Nagoya?
>
> Thanks
> -Vincent
--
Christopher Lenz
/=/ cmlenz at gmx.de
Re: [cactus] build failure - need help
Posted by Sam Ruby <ru...@apache.org>.
Sorry, I've been travelling.
http://nagoya.apache.org/~rubys/gump/data/
You should now have access to *all* of the outputs of the build.
- Sam Ruby
RE: [cactus] build failure - need help
Posted by Vincent Massol <vm...@pivolis.com>.
> -----Original Message-----
> From: Christopher Lenz [mailto:cmlenz@gmx.de]
> Sent: 09 June 2003 00:23
> To: Gump code and data
> Subject: Re: [cactus] build failure - need help
>
> Vincent Massol wrote:
> > Good idea Chris... However, there can only be one <javadoc> tag per
> > project, right? Thus we have to create a new project. But then this
new
>
> Only one <javadoc> tag, but:
>
> "If a given project wants to publish more than one javadoc set,
> multiple <description> elements like in
> <javadoc nested="java/build/docs/javadocs" project="xml-xerces2">
> <description dir="api">XML Standard API</description>
> <description dir="xni">Xerces Native Interface</description>
> <description dir="xerces">Xerces2 Implementation</description>
> <description dir="other">Other Classes</description>
> </javadoc>
> must be used."
> [http://jakarta.apache.org/gump/project.html#javadoc]
hehe... I should RTFM I guess :-)
Do you know if the javadoc is generated even when the project fails?
Thanks
-Vincent
[snip]
Re: [cactus] build failure - need help
Posted by Christopher Lenz <cm...@gmx.de>.
Vincent Massol wrote:
> Good idea Chris... However, there can only be one <javadoc> tag per
> project, right? Thus we have to create a new project. But then this new
Only one <javadoc> tag, but:
"If a given project wants to publish more than one javadoc set,
multiple <description> elements like in
<javadoc nested="java/build/docs/javadocs" project="xml-xerces2">
<description dir="api">XML Standard API</description>
<description dir="xni">Xerces Native Interface</description>
<description dir="xerces">Xerces2 Implementation</description>
<description dir="other">Other Classes</description>
</javadoc>
must be used."
[http://jakarta.apache.org/gump/project.html#javadoc]
BTW, jakarta-cactus-sample-servlet-XX doesn't have any real javadoc, AFAICT.
> project can't depend on the project it is debugging (otherwise it won't
> be run).
>
> Do you know if Gump algorithm will run projects in the order they are
> defined in once it has resolved project dependencies? I guess I'll have
> to look at the code...
>
> Any idea?
>
> Thanks
> -Vincent
>
>
>>-----Original Message-----
>>From: Christopher Lenz [mailto:cmlenz@gmx.de]
>>Sent: 08 June 2003 22:38
>>To: Gump code and data
>>Subject: Re: [cactus] build failure - need help
>>
>>Vincent Massol wrote:
>>
>>>Hi Adam,
>>>
>>>Unfortunately, in my case, "-debug" will not help. When the script
>>>starts tomcat, the tomcat output is redirected to a file. What I
>
> need is
>
>>>access to the built project so that I can have a look at the
>
> generated
>
>>>files. We simply need to put Gump working dir in an htdocs...
>>
>>Hmm, what about adding a <javadoc> element to the gump descriptor. If
>
> it
>
>>pointed to the directory to which the logs are written, wouldn't that
>>make them available?
>>
>>
>>>That said, being able to run with debug would be nice too in some
>>>occasions :-)
>>>
>>>Thanks
>>>-Vincent
>>>
>>>
>>>
>>>>-----Original Message-----
>>>>From: Adam Jack [mailto:ajack@TrySybase.com]
>>>>Sent: 08 June 2003 19:48
>>>>To: 'Gump code and data'
>>>>Subject: RE: [cactus] build failure - need help
>>>>
>>>>This is another example of why it'd be nice to be able to set debug
>
> on
>
>>>in
>>>
>>>
>>>>the gump descriptor, and have -debug passed to ant. Some build
>>>
>>>problems
>>>
>>>
>>>>can
>>>>be such that they work locally, but fail at the remote site. They
>
> need
>
>>>to
>>>
>>>
>>>>be
>>>>debugged at the remote site, IMHO.
>>>>
>>>>I've said it before, but I'll submit an enhancement request for it
>>>
>>>this
>>>
>>>
>>>>time.
>>>>
>>>>regards
>>>>
>>>>Adam
>>>>-----Original Message-----
>>>>From: Vincent Massol [mailto:vmassol@pivolis.com]
>>>>Sent: Friday, June 06, 2003 3:09 PM
>>>>To: gump@jakarta.apache.org
>>>>Subject: [cactus] build failure - need help
>>>>
>>>>
>>>>Hi,
>>>>
>>>>I need some help to diagnosis why the
>
> jakarta-cactus-sample-servlet-12
>
>>>>project is failing to build with Gump. The problem has to do with
>>>>starting Tomcat 3.x but the build output is not enough to diagnosis
>>>
>>>the
>>>
>>>
>>>>problem.
>>>>
>>>>During the build there is a file created:
>>>>
>>>
>>>
> jakarta-cactus/samples/servlet/target-12/test/test-reports/tomcat3x.out
>
>>>>Would it be possible to have access to this file?
>>>>
>>>>More generally is there a way to a web read access to the area where
>>>>Gump builds the projects on Nagoya?
>>>>
>>>>Thanks
>>>>-Vincent
>>
>>
>>--
>>Christopher Lenz
>>/=/ cmlenz at gmx.de
--
Christopher Lenz
/=/ cmlenz at gmx.de
RE: [cactus] build failure - need help
Posted by Vincent Massol <vm...@pivolis.com>.
Good idea Chris... However, there can only be one <javadoc> tag per
project, right? Thus we have to create a new project. But then this new
project can't depend on the project it is debugging (otherwise it won't
be run).
Do you know if Gump algorithm will run projects in the order they are
defined in once it has resolved project dependencies? I guess I'll have
to look at the code...
Any idea?
Thanks
-Vincent
> -----Original Message-----
> From: Christopher Lenz [mailto:cmlenz@gmx.de]
> Sent: 08 June 2003 22:38
> To: Gump code and data
> Subject: Re: [cactus] build failure - need help
>
> Vincent Massol wrote:
> > Hi Adam,
> >
> > Unfortunately, in my case, "-debug" will not help. When the script
> > starts tomcat, the tomcat output is redirected to a file. What I
need is
> > access to the built project so that I can have a look at the
generated
> > files. We simply need to put Gump working dir in an htdocs...
>
> Hmm, what about adding a <javadoc> element to the gump descriptor. If
it
> pointed to the directory to which the logs are written, wouldn't that
> make them available?
>
> > That said, being able to run with debug would be nice too in some
> > occasions :-)
> >
> > Thanks
> > -Vincent
> >
> >
> >>-----Original Message-----
> >>From: Adam Jack [mailto:ajack@TrySybase.com]
> >>Sent: 08 June 2003 19:48
> >>To: 'Gump code and data'
> >>Subject: RE: [cactus] build failure - need help
> >>
> >>This is another example of why it'd be nice to be able to set debug
on
> >
> > in
> >
> >>the gump descriptor, and have -debug passed to ant. Some build
> >
> > problems
> >
> >>can
> >>be such that they work locally, but fail at the remote site. They
need
> >
> > to
> >
> >>be
> >>debugged at the remote site, IMHO.
> >>
> >>I've said it before, but I'll submit an enhancement request for it
> >
> > this
> >
> >>time.
> >>
> >>regards
> >>
> >>Adam
> >>-----Original Message-----
> >>From: Vincent Massol [mailto:vmassol@pivolis.com]
> >>Sent: Friday, June 06, 2003 3:09 PM
> >>To: gump@jakarta.apache.org
> >>Subject: [cactus] build failure - need help
> >>
> >>
> >>Hi,
> >>
> >>I need some help to diagnosis why the
jakarta-cactus-sample-servlet-12
> >>project is failing to build with Gump. The problem has to do with
> >>starting Tomcat 3.x but the build output is not enough to diagnosis
> >
> > the
> >
> >>problem.
> >>
> >>During the build there is a file created:
> >>
> >
> >
jakarta-cactus/samples/servlet/target-12/test/test-reports/tomcat3x.out
> >
> >>Would it be possible to have access to this file?
> >>
> >>More generally is there a way to a web read access to the area where
> >>Gump builds the projects on Nagoya?
> >>
> >>Thanks
> >>-Vincent
>
>
> --
> Christopher Lenz
> /=/ cmlenz at gmx.de
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: gump-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: gump-help@jakarta.apache.org
Re: [cactus] build failure - need help
Posted by Christopher Lenz <cm...@gmx.de>.
Vincent Massol wrote:
> Hi Adam,
>
> Unfortunately, in my case, "-debug" will not help. When the script
> starts tomcat, the tomcat output is redirected to a file. What I need is
> access to the built project so that I can have a look at the generated
> files. We simply need to put Gump working dir in an htdocs...
Hmm, what about adding a <javadoc> element to the gump descriptor. If it
pointed to the directory to which the logs are written, wouldn't that
make them available?
> That said, being able to run with debug would be nice too in some
> occasions :-)
>
> Thanks
> -Vincent
>
>
>>-----Original Message-----
>>From: Adam Jack [mailto:ajack@TrySybase.com]
>>Sent: 08 June 2003 19:48
>>To: 'Gump code and data'
>>Subject: RE: [cactus] build failure - need help
>>
>>This is another example of why it'd be nice to be able to set debug on
>
> in
>
>>the gump descriptor, and have -debug passed to ant. Some build
>
> problems
>
>>can
>>be such that they work locally, but fail at the remote site. They need
>
> to
>
>>be
>>debugged at the remote site, IMHO.
>>
>>I've said it before, but I'll submit an enhancement request for it
>
> this
>
>>time.
>>
>>regards
>>
>>Adam
>>-----Original Message-----
>>From: Vincent Massol [mailto:vmassol@pivolis.com]
>>Sent: Friday, June 06, 2003 3:09 PM
>>To: gump@jakarta.apache.org
>>Subject: [cactus] build failure - need help
>>
>>
>>Hi,
>>
>>I need some help to diagnosis why the jakarta-cactus-sample-servlet-12
>>project is failing to build with Gump. The problem has to do with
>>starting Tomcat 3.x but the build output is not enough to diagnosis
>
> the
>
>>problem.
>>
>>During the build there is a file created:
>>
>
> jakarta-cactus/samples/servlet/target-12/test/test-reports/tomcat3x.out
>
>>Would it be possible to have access to this file?
>>
>>More generally is there a way to a web read access to the area where
>>Gump builds the projects on Nagoya?
>>
>>Thanks
>>-Vincent
--
Christopher Lenz
/=/ cmlenz at gmx.de
RE: [cactus] build failure - need help
Posted by Vincent Massol <vm...@pivolis.com>.
Hi Adam,
Unfortunately, in my case, "-debug" will not help. When the script
starts tomcat, the tomcat output is redirected to a file. What I need is
access to the built project so that I can have a look at the generated
files. We simply need to put Gump working dir in an htdocs...
That said, being able to run with debug would be nice too in some
occasions :-)
Thanks
-Vincent
> -----Original Message-----
> From: Adam Jack [mailto:ajack@TrySybase.com]
> Sent: 08 June 2003 19:48
> To: 'Gump code and data'
> Subject: RE: [cactus] build failure - need help
>
> This is another example of why it'd be nice to be able to set debug on
in
> the gump descriptor, and have -debug passed to ant. Some build
problems
> can
> be such that they work locally, but fail at the remote site. They need
to
> be
> debugged at the remote site, IMHO.
>
> I've said it before, but I'll submit an enhancement request for it
this
> time.
>
> regards
>
> Adam
> -----Original Message-----
> From: Vincent Massol [mailto:vmassol@pivolis.com]
> Sent: Friday, June 06, 2003 3:09 PM
> To: gump@jakarta.apache.org
> Subject: [cactus] build failure - need help
>
>
> Hi,
>
> I need some help to diagnosis why the jakarta-cactus-sample-servlet-12
> project is failing to build with Gump. The problem has to do with
> starting Tomcat 3.x but the build output is not enough to diagnosis
the
> problem.
>
> During the build there is a file created:
>
jakarta-cactus/samples/servlet/target-12/test/test-reports/tomcat3x.out
>
> Would it be possible to have access to this file?
>
> More generally is there a way to a web read access to the area where
> Gump builds the projects on Nagoya?
>
> Thanks
> -Vincent
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: gump-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: gump-help@jakarta.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: gump-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: gump-help@jakarta.apache.org
RE: [cactus] build failure - need help
Posted by Adam Jack <aj...@TrySybase.com>.
This is another example of why it'd be nice to be able to set debug on in
the gump descriptor, and have -debug passed to ant. Some build problems can
be such that they work locally, but fail at the remote site. They need to be
debugged at the remote site, IMHO.
I've said it before, but I'll submit an enhancement request for it this
time.
regards
Adam
-----Original Message-----
From: Vincent Massol [mailto:vmassol@pivolis.com]
Sent: Friday, June 06, 2003 3:09 PM
To: gump@jakarta.apache.org
Subject: [cactus] build failure - need help
Hi,
I need some help to diagnosis why the jakarta-cactus-sample-servlet-12
project is failing to build with Gump. The problem has to do with
starting Tomcat 3.x but the build output is not enough to diagnosis the
problem.
During the build there is a file created:
jakarta-cactus/samples/servlet/target-12/test/test-reports/tomcat3x.out
Would it be possible to have access to this file?
More generally is there a way to a web read access to the area where
Gump builds the projects on Nagoya?
Thanks
-Vincent
---------------------------------------------------------------------
To unsubscribe, e-mail: gump-unsubscribe@jakarta.apache.org
For additional commands, e-mail: gump-help@jakarta.apache.org