testing javadoc

[Andrew McIntyre <mc...@gmail.com>]

On 2/23/07, Dag H. Wanvik <Da...@sun.com> wrote:
>
> Is there a reason why the testing javadocs are not generated by the
> javadoc target? I noticed they were not.. and I needed to consult them
> on getting up top speed on the JUnit framework.

Inertia? Procrastination? Because this is only the second time anyone
has brought it up? :-)

Dan and I talked about it a while ago, but no one seemed very
interested at the time and I had put it on the back burner because I
knew there would be a lot of javadoc errors lurking in the test tree.
But, I've been wanting javadoc for the test tree lately, too.

So, I cleaned up all the javadoc in the test hierarchy up and made a
target for it. With revision 511226 I've made a new target
'testingdocs' to javadoc the test tree and hooked it into the
top-level javadoc target.

Note that I left out the jdbc4 test suite from the target, as I didn't
have jdk16 on my machine at the moment. If someone else would like to
create an alternate target that docs everything if jdk16 is available,
they should feel free to do so. Since I didn't try to build the jdbc4
test javadoc, I'd bet that there are still some javadoc errors hiding
in there.

Committed too late for the javadoc build that gets synced to the
website, but it should show up at:

http://db.apache.org/derby/javadoc/testing/

tomorrow.

cheers,
andrew

Re: testing javadoc

["Dag H. Wanvik" <Da...@Sun.COM>]

> Also realized in the meantime that the next javadoc build that will be
> synced to the website will be Monday evening PST, early morning
> Norway-time, and should include the jdbc4 test suite in the javadoc.

Great! Thanks, Andrew :)

Dag

Andrew McIntyre <mc...@gmail.com> writes:

> On 2/23/07, Andrew McIntyre <mc...@gmail.com> wrote:
>>
>> Note that I left out the jdbc4 test suite from the target, as I didn't
>> have jdk16 on my machine at the moment. If someone else would like to
>> create an alternate target that docs everything if jdk16 is available,
>> they should feel free to do so. Since I didn't try to build the jdbc4
>> test javadoc, I'd bet that there are still some javadoc errors hiding
>> in there.
>
> So, I came up with a quick easy solution for this too and just
> committed it. After revision 511229, if the property jdk16 is set, the
> jdbc4 test suite will be javadoc'd along with the rest of the tests.
> If not, it is excluded.
>
>> Committed too late for the javadoc build that gets synced to the
>> website, but it should show up at:
>>
>> http://db.apache.org/derby/javadoc/testing/
>>
>> tomorrow.
>
> Also realized in the meantime that the next javadoc build that will be
> synced to the website will be Monday evening PST, early morning
> Norway-time, and should include the jdbc4 test suite in the javadoc.
>
> andrew
>

-- 
Dag H. Wanvik
Sun Microsystems, Database Technology Group (DBTG)
Haakon VII gt. 7b, N-7485 Trondheim, Norway
Tel: x43496/+47 73842196, Fax:  +47 73842101

Re: testing javadoc

[Andrew McIntyre <mc...@gmail.com>]

On 2/23/07, Andrew McIntyre <mc...@gmail.com> wrote:
>
> Note that I left out the jdbc4 test suite from the target, as I didn't
> have jdk16 on my machine at the moment. If someone else would like to
> create an alternate target that docs everything if jdk16 is available,
> they should feel free to do so. Since I didn't try to build the jdbc4
> test javadoc, I'd bet that there are still some javadoc errors hiding
> in there.

So, I came up with a quick easy solution for this too and just
committed it. After revision 511229, if the property jdk16 is set, the
jdbc4 test suite will be javadoc'd along with the rest of the tests.
If not, it is excluded.

> Committed too late for the javadoc build that gets synced to the
> website, but it should show up at:
>
> http://db.apache.org/derby/javadoc/testing/
>
> tomorrow.

Also realized in the meantime that the next javadoc build that will be
synced to the website will be Monday evening PST, early morning
Norway-time, and should include the jdbc4 test suite in the javadoc.

andrew