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 comple
Perry, thanks for procedure, it worked for me!
Is someone collecting JDK 1.4.0 related bugs?
Bruce
>>> [EMAIL PROTECTED] 04/14/02 11:34PM >>>
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
ut 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 Cocoo
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]
Subje
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
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
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:
>Ye
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 a
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
Stock Sun JDK1.3.1, empty classpath, Cocoon from CVS, "build.bat
javadocs" works. Do you run JDK1.4?
Also it doesn't matter, OS is Win2K.
Vadim
> From: Marc Jeffrey Driftmeyer [mailto:[EMAIL PROTECTED]]
>
> Vadim,
>
> I'm happy for your success but that does not address the error message
> I'
Vadim,
I'm happy for your success but that does not address the error message
I'm receiving. What is your build environment?
-Marc
Vadim Gritsenko wrote:
>>From: Marc Jeffrey Driftmeyer [mailto:[EMAIL PROTECTED]]
>>
>>Of course that is the command..
>>
>>
>>And as run the latest snapshot or
I use jdk1.3.1, and the rest does not matter for javadoc.
Vadim
> From: Bruce Krautbauer [mailto:[EMAIL PROTECTED]]
>
> 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
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
> 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
> [jav
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.ja
In Java world, API docs are generated from the source code.
IIRC, "build javadocs" command launched from the Cocoon source
distribution root dir will build you all Cocoon API documentation, in
the ./build/cocoon/javadocs directory.
Once you have javadocs, you can copy them into the Cocoon's samp
16 matches
Mail list logo
