>I found javadoc had a hard dependency on ../etc/common.xml
Where is common.xml? I dont know any. Can you point it to me?
http://svn.apache.org/repos/asf/ant/core/trunk/
>BUILD FAILED
>java.lang.NullPointerException
>at
org.apache.tools.ant.types.AbstractFileSet.setupDirectoryScanner(A
ontent contained within this
> transmission.
>
>
>
>
> > Date: Tue, 3 Mar 2009 09:52:04 -0600
> > Subject: JavaDoc problem
> > From: troy.b...@gmail.com
> > To: user@ant.apache.org
> >
> > Greetings
> >
> > I have a "build system&quo
Sender. This transmission is of a confidential nature and Sender does not
endorse distribution to any party other than intended recipient. Sender does
not necessarily endorse content contained within this transmission.
> Date: Tue, 3 Mar 2009 09:52:04 -0600
> Subject: JavaDoc problem
Greetings
I have a "build system" built around ant. It was originally written with
ant 1.6.5, recently I tried to upgrade to 1.7.1 and my javadoc task started
failing with a NullPointer exception. Does anyone know if this is a known
issue or is there something I can do? Switching back to 1.6.5
I'm having an odd problem with a Javadoc task in Ant 1.6.5. I'm using
Eclipse but I have a second copy of Ant 1.6.5 outside of Eclipse and the
exact same thing happens regardless of whether I run the build within
Eclipse or outside of it.
The Javadoc is writing the docs for 5 packages. I've cr
Hello Rhino,
I think javadoc has a classpath attribute.
You presumably need to put in the javadoc classpath the jar containing
this common.Utilities class (or the root directory containing the
corresponding classes). Normally the classpath you use to compile a module
is also OK to run javadoc.
Chee
I need some guidance on how to prevent a specific warning message from a
Javadoc task in Ant 1.6.2.
One of the programs for which I am generating Javadocs contains the line:
import common.Utilities;
This line causes the following warning in my Ant build:
[javadoc]
E:\eclipse\3.0.1\eclipse\works
