Seems as though it might be an issue with the change in the javadoc options
for 1.4
In the build log, it has an error with:

org.apache.cocoon.components.language.programming.java

Tried playing with javadoc outside of build & ant.
Build invokes javadoc, with a list of o.a.c.xxx for each package, but I
think the new javadoc expects those to be actual files and doesn't find them
so produces nothing! The only one that looks like a file in the list,
o.a.c.c.l.programming.java, doesn't exist!

javadoc 1.4 has introduced an option -subpackages, which probably makes the
list of o.a.c.xxx's redundant. I finally got it to work, manually, with
"-subpackages org.apache.cocoon", but the current Cocoon version of ant
won't take the subpackages option, so I can't see a proper fix at this
stage. In the end, I suppose ant would need to be modified to account for
these differences between 1.3 and 1.4 javadoc.

But to do it manually, run "build javadocs -verbose" and redirect output to
a log file. Edit the log file to find and extract the very long javadoc
command line into a separate file. You now need to reduce this to just the
parameters and options, so remove the leading ...javadoc.exe and replace all
the package names at the end, i.e everything after -version -author, with
-subpackages org.apache.cocoon

Now execute: javadoc @file (where file is the one you just created,
containing the javadoc parameters and options). The above assumes your under
Windoze.

Sorry this is a bit involved, I tried to fake out the ant build, but
couldn't get around it's checks!

HTH

Perry

-----Original Message-----
From: Marc Jeffrey Driftmeyer [mailto:[EMAIL PROTECTED]]
Sent: Monday, 15 April 2002 10:47
To: [EMAIL PROTECTED]
Subject: Re: Missing API Docs in Cocoon 2.0.2 and latest CVS


I completely agree and that sort of Wonderful SQA bugs should not go 
unnoticed.

-Marc

Andrew C. Oliver wrote:

>Not sure what all the issues are...all I know is what works on 1.3.1
>buildwise often doesn't work on 1.4.0.  
>
>The horrible bug is that the doc build can be "SUCCESSFUL" even if it
>fails.  (thats bad)
>
>On Sun, 2002-04-14 at 20:09, Marc Jeffrey Driftmeyer wrote:
>
>>I have a hard time believing that this permissions issue of reading into 
>>that path is the fault of Sun's JDK.  I have a greater suspicion it has 
>>to do with some build issues within Cocoon, since we already know that 
>>Cocoon 2.0.2 build SDK of choice is 1.3.1.
>>
>>-Marc
>>
>>Andrew C. Oliver wrote:
>>
>>>Yeah, I can't get the javadoc to generate under 1.4.0 either.  What's
>>>worse is it fails and then says "BUILD SUCCESSFUL".  I regard the first
>>>problem as a small glitch that can probably even be resolved by waiting
>>>for 1.4.0_01...  The second is a horrible evil bug. ;-)
>>>
>>>-Andy
>>>
>>>On Sun, 2002-04-14 at 02:23, Marc Jeffrey Driftmeyer wrote:
>>>
>>>>Bruce,
>>>>
>>>>I'm running Windows XP Professional, Java SDK 1.4.0 and Tomcat 4.0.4b2.
>>>>
>>>>-Marc
>>>>
>>>>Bruce Krautbauer wrote:
>>>>
>>>>>I just did a cvs checkout -r HEAD xml-cocoon2 to a new directory,
copied xercesImpl-2.0.0.jar, xalan-2.3.1.jar, and the xml-apis.jar from the
.\lib\core\ to the %JAVA_HOME%\jre\lib\endorsed\ directory and my build
javadocs gives the same result as Marc's.  Everything else seems to build
and run fine.  It must be an environment issue.  I'm running Win 2KSP2, JDK
1.4.0, Tomcat 4.0.4b2.  Marc and Vadim, what are you running?
>>>>>
>>>>>Bruce
>>>>>
>>>>>>>>[EMAIL PROTECTED] 04/11/02 11:34AM >>>
>>>>>>>>
>>>>>>From: Marc Jeffrey Driftmeyer [mailto:[EMAIL PROTECTED]] 
>>>>>>
>>>>>>Of course that is the command..
>>>>>>
>>>>>>
>>>>>>And as run the latest snapshot or even the cocoon 2.0.2 release here
>>>>>>
>>>>>is
>>>>>
>>>>>>the error log for the javadocs.
>>>>>>
>>>>>>javadocs:
>>>>>>[javadoc] Generating Javadoc
>>>>>>[javadoc] Javadoc execution
>>>>>>[javadoc] Loading source file
>>>>>>org.apache.cocoon.components.language.programming.java...
>>>>>>[javadoc] error: cannot read:
>>>>>>org.apache.cocoon.components.language.programming.java
>>>>>>
>>>>>...
>>>>>
>>>>>>[javadoc] 1 error
>>>>>>
>>>>>I just tried "build javadocs":
>>>>>
>>>>>[javadoc] Generating
>>>>>C:\Apache\xml-cocoon2\build\cocoon\javadocs\help-doc.html...
>>>>>[javadoc] 116 warnings
>>>>>
>>>>>Result is 842 files in the cocoon/build/cocoon/javadocs.
>>>>>
>>>>>
>>>>>Vadim
>>>>>
>>>>>
>>>>>
>>>>>---------------------------------------------------------------------
>>>>>Please check that your question has not already been answered in the
>>>>>FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
>>>>>
>>>>>To unsubscribe, e-mail: <[EMAIL PROTECTED]>
>>>>>For additional commands, e-mail: <[EMAIL PROTECTED]>
>>>>>
>>>>//
>>>>
>>>>
>>>>
>>>>
>>>>---------------------------------------------------------------------
>>>>Please check that your question has not already been answered in the
>>>>FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
>>>>
>>>>To unsubscribe, e-mail: <[EMAIL PROTECTED]>
>>>>For additional commands, e-mail: <[EMAIL PROTECTED]>
>>>>
>>//
>>
>>
>>
>>
>>---------------------------------------------------------------------
>>Please check that your question has not already been answered in the
>>FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
>>
>>To unsubscribe, e-mail: <[EMAIL PROTECTED]>
>>For additional commands, e-mail: <[EMAIL PROTECTED]>
>>


---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>

---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>

Reply via email to