You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ant.apache.org by Jay Glanville <di...@nortelnetworks.com> on 2001/05/15 15:32:27 UTC
RE: how to get more debug information [HELP!]
Ok. I STILL need help with this problem. Please help, before I start
sending pictures of myself on my knees begging! ;-)
Here's the situation so far:
- uname -sr = SunOS 5.6
- trying to run javadoc, but it continuously returns -1 (see original
posting below)
- I tried running the command on the command line without success (it seems
that sh on SunOS has a 256 character limit.
- to solve the previous problem, I made changes to my version of <javadoc>
so that it would use the @file command line parameter to shorten the javadoc
command line
- the javadoc task still fails, but if I cut and paste the command into an
xterm, it succeeds.
- the major problem that I'm having with the javadoc task is not that it's
failing, but that it's not telling me why it's failing (it just shows
"return -1")
- I've tried to make changes to Javadoc.java and Execute.java (the actual
class that runs the javadoc command) to properly redirect the error output
from the command so that I can see why it fails, but totally without
success. Can anyone point me to the right place to make the changes so that
I can properly capture the output?
Please, please, how do I find out why the command is failing? Heck, I
wouldn't care about why, as much as how to solve the problem (but I really
can't do that until I find out why ...)
So, please, don't make me send pictures ... please help. ;-)
JDGlanville
> -----Original Message-----
> From: Stephane Bailliez [mailto:sbailliez@imediation.com]
> Sent: Thursday, May 10, 2001 3:27 PM
> To: ant-user@jakarta.apache.org
> Subject: RE: how to get more debug information
>
>
>
> Try running the javadoc in the command line with the same
> options. With luck
> you may have more information.
>
> I have had problem myself on Solaris and javadoc via ant but
> didn't had time
> to dig into the code and find the problem. It had problem with the
> windowtitle and title which were amazingly unquoted (and
> there was space in
> it) while the line was ok under nt.
>
> --
> Stéphane Bailliez
> Software Engineer, Paris - France
> iMediation - http://www.imediation.com
> Disclaimer: All the opinions expressed above are mine and
> not those from my
> company.
>
>
>
> > -----Original Message-----
> > From: Jay Glanville [mailto:dickon@nortelnetworks.com]
> > Sent: Thursday, May 10, 2001 8:26 PM
> > To: Ant-User (text)
> > Subject: how to get more debug information
> >
> >
> > I'm trying to run a javadoc command and it's failing. So, in
> > an attempt to
> > determine why it's failing, I run ant with a -debug option to
> > get all the
> > information. The following is a snippet of the resulting log:
> >
> > [javadoc] Generating Javadoc
> > [javadoc] Source path = /vobs/SiteManager/src
> > [javadoc] Packages = [com.nortel.smfw.*]
> > [javadoc] Exclude Packages = []
> > [javadoc] Javadoc args: javadoc -d
> /vobs/SiteManager/build/javadocs
> > -extdirs /vobs/SiteManager/lib -J-Xmx128m -classpath
> > /vobs/SiteManager/src
> > -sourcepath /vobs/SiteManager/src -version -author
> > com.nortel.smfw.base
> > [...snipped...]
> > [javadoc] Javadoc execution
> > Execute:Java13CommandLauncher: javadoc -d
> > /vobs/SiteManager/build/javadocs
> > -extdirs /vobs/SiteManager/lib -J-Xmx128m -classpath
> > /vobs/SiteManager/src
> > -sourcepath /vobs/SiteManager/src -version -author
> > com.nortel.smfw.base
> > [...snipped...]
> >
> > BUILD FAILED
> >
> > /vobs/SiteManager/bin/build.xml:247: Javadoc returned -1
> >
> >
> > What is causing the -1? I know that javadoc is in my path
> > because the shell
> > script that I use to start ant sets up the necessary path for
> > me. How can I
> > find more information?
> >
> > --
> > Jay Dickon Glanville
> > P068 - SiteManager Development, Nortel Networks
> > 613-765-1144 (ESN 395-1144)
> > MS: 045/55/A05
> > E-Mail: dickon@nortelnetworks.com
> >
>
Re: how to get more debug information [HELP!]
Posted by Stefan Bodewig <bo...@apache.org>.
Jay Glanville <di...@nortelnetworks.com> wrote:
> - the javadoc task still fails, but if I cut and paste the command
> into an xterm, it succeeds.
wild guess, does your antRun script contain cariage returns? See the
FAQ at <http://jakarta.apache.org/ant/faq.html>, topic is something
like "cvs doesn't work" in the known problems section (no HTTP access,
so I cannot check ATM).
Stefan
RE: how to get more debug information [HELP!]
Posted by Diane Holt <ho...@yahoo.com>.
Jay,
When I try running the example for <javadoc> in the manual (I wanted
something that would fail), I do see the error messages from 'javadoc', so
I'm not sure why you're not seeing yours. Can you try doing something like
that and seeing whether the error messages get printed?
Diane
--- Jay Glanville <di...@nortelnetworks.com> wrote:
> Ok. I STILL need help with this problem. Please help, before I start
> sending pictures of myself on my knees begging! ;-)
>
> Here's the situation so far:
> - uname -sr = SunOS 5.6
> - trying to run javadoc, but it continuously returns -1 (see original
> posting below)
> - I tried running the command on the command line without success (it
> seems
> that sh on SunOS has a 256 character limit.
> - to solve the previous problem, I made changes to my version of
> <javadoc>
> so that it would use the @file command line parameter to shorten the
> javadoc
> command line
> - the javadoc task still fails, but if I cut and paste the command into
> an
> xterm, it succeeds.
> - the major problem that I'm having with the javadoc task is not that
> it's
> failing, but that it's not telling me why it's failing (it just shows
> "return -1")
> - I've tried to make changes to Javadoc.java and Execute.java (the
> actual
> class that runs the javadoc command) to properly redirect the error
> output
> from the command so that I can see why it fails, but totally without
> success. Can anyone point me to the right place to make the changes so
> that
> I can properly capture the output?
>
> Please, please, how do I find out why the command is failing? Heck, I
> wouldn't care about why, as much as how to solve the problem (but I
> really
> can't do that until I find out why ...)
>
> So, please, don't make me send pictures ... please help. ;-)
>
> JDGlanville
>
> > -----Original Message-----
> > From: Stephane Bailliez [mailto:sbailliez@imediation.com]
> > Sent: Thursday, May 10, 2001 3:27 PM
> > To: ant-user@jakarta.apache.org
> > Subject: RE: how to get more debug information
> >
> >
> >
> > Try running the javadoc in the command line with the same
> > options. With luck
> > you may have more information.
> >
> > I have had problem myself on Solaris and javadoc via ant but
> > didn't had time
> > to dig into the code and find the problem. It had problem with the
> > windowtitle and title which were amazingly unquoted (and
> > there was space in
> > it) while the line was ok under nt.
> >
> > --
> > St�phane Bailliez
> > Software Engineer, Paris - France
> > iMediation - http://www.imediation.com
> > Disclaimer: All the opinions expressed above are mine and
> > not those from my
> > company.
> >
> >
> >
> > > -----Original Message-----
> > > From: Jay Glanville [mailto:dickon@nortelnetworks.com]
> > > Sent: Thursday, May 10, 2001 8:26 PM
> > > To: Ant-User (text)
> > > Subject: how to get more debug information
> > >
> > >
> > > I'm trying to run a javadoc command and it's failing. So, in
> > > an attempt to
> > > determine why it's failing, I run ant with a -debug option to
> > > get all the
> > > information. The following is a snippet of the resulting log:
> > >
> > > [javadoc] Generating Javadoc
> > > [javadoc] Source path = /vobs/SiteManager/src
> > > [javadoc] Packages = [com.nortel.smfw.*]
> > > [javadoc] Exclude Packages = []
> > > [javadoc] Javadoc args: javadoc -d
> > /vobs/SiteManager/build/javadocs
> > > -extdirs /vobs/SiteManager/lib -J-Xmx128m -classpath
> > > /vobs/SiteManager/src
> > > -sourcepath /vobs/SiteManager/src -version -author
> > > com.nortel.smfw.base
> > > [...snipped...]
> > > [javadoc] Javadoc execution
> > > Execute:Java13CommandLauncher: javadoc -d
> > > /vobs/SiteManager/build/javadocs
> > > -extdirs /vobs/SiteManager/lib -J-Xmx128m -classpath
> > > /vobs/SiteManager/src
> > > -sourcepath /vobs/SiteManager/src -version -author
> > > com.nortel.smfw.base
> > > [...snipped...]
> > >
> > > BUILD FAILED
> > >
> > > /vobs/SiteManager/bin/build.xml:247: Javadoc returned -1
> > >
> > >
> > > What is causing the -1? I know that javadoc is in my path
> > > because the shell
> > > script that I use to start ant sets up the necessary path for
> > > me. How can I
> > > find more information?
> > >
> > > --
> > > Jay Dickon Glanville
> > > P068 - SiteManager Development, Nortel Networks
> > > 613-765-1144 (ESN 395-1144)
> > > MS: 045/55/A05
> > > E-Mail: dickon@nortelnetworks.com
> > >
> >
>
=====
(holtdl@yahoo.com)
__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/