Re: [cactus] build failure - need help

[Christopher Lenz]

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:[EMAIL PROTECTED]
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:[EMAIL PROTECTED]
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:[EMAIL PROTECTED]
Sent: Friday, June 06, 2003 3:09 PM
To: [EMAIL PROTECTED]
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]