Conor MacNeill wrote:
>
> I have a suggestion for Gump. I'm not that familiar with the current Gump
> implementation, but what I would like to do is have access to Ant's debug
> output from the Gump page.
>
> To do that, Gump could use a listener, such as the XmlLogger or even a
> GumpListener, to capture the Ant output. By default this would be styled to
> show the same output as Gump currently shows, such as
> http://jakarta.apache.org/builds/gump/latest/dist-ant.html
> for example.
>
> The idea would be that this page would provide a link to debug output,
> something like
> http://jakarta.apache.org/builds/gump/latest/dist-ant.html?debug
> which would provide the full Ant debug output. We could even support viewing
> at the verbose level. This may make it easier to understand some Gump
> failures such as the one currently occurring on jakarta-turbine-fulcrum.
>
> I can help out but thought I'd gather some feedback first.
Let me apologize in advance. Please forgive my roundabout answer. And Jon
and Jason, please follow along too. And Geir, please chime in as I've
recently taken you through this same process...
Depending on your operating system, adjust and execute one of the lines in
the first section below. Then execute the second set in its entirety.
Then execute one of the lines in the third section below.
export
CLASSPATH=.:/usr/java/jdk1.3.1/lib/tools.jar:/usr/java/jdk1.3.1/jre/lib/rt.jar
SET CLASSPATH=.;C:\jdk1.3.1\lib\tools.jar
wget http://www.apache.org/~rubys/gump-fulcrum.zip
cvs co jakarta-turbine-fulcrum
unzip gump-fulcrum.zip
cd jakarta-turbine-fulcrum
sh build.sh
call build.bat
Now, if you have successfully reproduced the turbine-fulcrum failure, then
you have also demonstrated that you have everything you need to execute the
scripts generated by gump. In order to generate the scripts you also have
an additional dependency: either JAXP1.1 or Xalan2. Your choice.
Once reproduced, Isolating the failure is generally as simple as replacing
jars with "known good ones" until the problem goes away. That, coupled
with knowledge of what day the problem first appeared is usually enough
information. Unfortunately, turbine-fulcrum has been broken for over a
week. That saddens me. I realize that jvz has been in vacation mode
during this time, but it leads me to wonder - is he the only one who cares?
If you take a peek inside the build script, you can get a glimpse of how
gump works. Essentially, all gump does is run Ant from the command line,
with the classpath and command line arguments set up appropriately. Stdout
is captured and the results are inserted into a fixed location on a
statically generated html page. There is no server processing involved in
the pages you see. An alternative to "dist-ant?debug.html" would perhaps
be "debug_dist-ant.html". Or .xml. Or .zip.
At this point, you can also easily see how to turn on Ant debug for
yourself. However, I'm reasonably confident that it will not shed much
light on this particular problem. However, if you still desire this
information, mark up the build scripts and send them back to here. I'll
incorporate the change and upload the results daily.
- Sam Ruby
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
