Issues with Javadoc

Thread view:

Elspeth Thorne - 17 May 2004 10:35 GMT

Hi,

I'm trying to document my package. It contains elements from Struts 1.1, and
Junit, as well as the standard java libraries.

When I run javadoc:

javadoc *.java

it gives me quite a few warnings, essentially not recognising any of the struts
calls.

I think it's a classpath problem, but I'm not sure.

Here is some output:

Constructing Javadoc information...
RequestAction.java:20: package org.apache.struts.action does not exist
import org.apache.struts.action.Action;
^
RequestAction.java:21: package org.apache.struts.action does not exist
import org.apache.struts.action.ActionForm;
^
RequestAction.java:22: package org.apache.struts.action does not exist
import org.apache.struts.action.ActionForward;
^
RequestAction.java:23: package org.apache.struts.action does not exist
import org.apache.struts.action.ActionMapping;
^

Any assistance would be appreciated.

Regards,

Elspeth Thorne.

Reply to this Message

Michael Amling - 17 May 2004 02:49 GMT

> I'm trying to document my package. It contains elements from Struts 1.1,
> and Junit, as well as the standard java libraries.
[quoted text clipped - 14 lines]
> import org.apache.struts.action.Action;
> ^

Is there an org.apache.struts.action.Action class in the CLASSPATH
that's in effect when you run javadoc? If not, you need to add it to
your CLASSPATH.

--Mike Amling

Reply to this Message

Elspeth Thorne - 17 May 2004 11:02 GMT

>> I'm trying to document my package. It contains elements from Struts
>> 1.1, and Junit, as well as the standard java libraries.
[quoted text clipped - 20 lines]
>
> --Mike Amling

Unless javadoc is using a different classpath from than that revealed by 'env' -
it's in there all right. This is why I'm somewhat confused.

Elspeth.

Reply to this Message

Michael Amling - 17 May 2004 04:00 GMT

>>> I'm trying to document my package. It contains elements from Struts
>>> 1.1, and Junit, as well as the standard java libraries.
[quoted text clipped - 20 lines]
> Unless javadoc is using a different classpath from than that revealed by
> 'env' - it's in there all right. This is why I'm somewhat confused.

To prove that org.apache.struts.action.Action is in the CLASSPATH, try

java org.apache.struts.action.Action

If you get an error message saying that Action has no method 'main',
that proves that the class is on the CLASSPATH, in which case I'd wonder
if your javadoc command has specified -classpath and/or -bootclasspath.

--Mike Amling

Reply to this Message

Issues with Javadoc

Free Magazines