Return-Path: 
 <derby-dev-return-52256-apmail-db-derby-dev-archive=db.apache.org@db.apache.org>
Delivered-To: apmail-db-derby-dev-archive@www.apache.org
Received: (qmail 13096 invoked from network); 12 Dec 2007 13:10:15 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 12 Dec 2007 13:10:15 -0000
Received: (qmail 20845 invoked by uid 500); 12 Dec 2007 13:10:04 -0000
Delivered-To: apmail-db-derby-dev-archive@db.apache.org
Received: (qmail 20633 invoked by uid 500); 12 Dec 2007 13:10:03 -0000
Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:derby-dev-help@db.apache.org>
List-Unsubscribe: <mailto:derby-dev-unsubscribe@db.apache.org>
List-Post: <mailto:derby-dev@db.apache.org>
List-Id: <derby-dev.db.apache.org>
Reply-To: <derby-dev@db.apache.org>
Delivered-To: mailing list derby-dev@db.apache.org
Received: (qmail 20623 invoked by uid 99); 12 Dec 2007 13:10:03 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Dec 2007 05:10:03 -0800
X-ASF-Spam-Status: No, hits=-1.0 required=10.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: local policy)
Received: from [192.18.6.21] (HELO gmp-eb-mail-1.sun.com) (192.18.6.21)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Dec 2007 13:10:04 +0000
Received: from fe-emea-10.sun.com (gmp-eb-lb-2-fe3.eu.sun.com [192.18.6.12])
	by gmp-eb-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id lBCD9ehK001520
	for <derby-dev@db.apache.org>; Wed, 12 Dec 2007 13:09:43 GMT
Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 id <0JSX00G01TC8MU00@fe-emea-10.sun.com>
 (original mail from Dag.Wanvik@Sun.COM) for derby-dev@db.apache.org; Wed,
 12 Dec 2007 13:09:40 +0000 (GMT)
Received: from khepri23.norway.sun.com ([129.159.112.235])
 by fe-emea-10.sun.com
 (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007))
 with ESMTPSA id <0JSX00BJVTVT5410@fe-emea-10.sun.com> for
 derby-dev@db.apache.org; Wed, 12 Dec 2007 13:09:29 +0000 (GMT)
Date: Wed, 12 Dec 2007 14:09:29 +0100
From: Dag.Wanvik@Sun.COM (Dag H. Wanvik)
Subject: Re: Javadoc build problems with JDK 1.5 code?
In-reply-to: <47526416.8090501@sun.com>
Sender: Dag.Wanvik@Sun.COM
To: derby-dev@db.apache.org
Message-id: <x1oxlk80ys8m.fsf@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
References: <4702FC9C.4030107@amberpoint.com> <wjo8r6kc1wni.fsf@sun.com>
 <4703A65A.5030708@amberpoint.com> <wjo8641o1boz.fsf@sun.com>
 <47041478.4070908@amberpoint.com> <4704FB0C.3050709@amberpoint.com>
 <47526416.8090501@sun.com>
User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/22.1 (usg-unix-v)
X-Virus-Checked: Checked by ClamAV on apache.org

Martin Zaun <Martin.Zaun@Sun.COM> writes:

> Hi,
> running 'ant javadoc' in the trunk aborts with jdk-1.5-related errors.
> I was wondering if they've been worked on already, since there was an
> old email thread and we decided to require JDK 1.5.
>
> Also, I'd like to use the {@code ...} tag for easy quoting of verbatim
> text in javadocs, which requires JDK 1.5.
>
> To fix the javadoc errors, I simply had to increase the "vmlevel" value
> to "1.5" under:  <target name="testing-javadoc-14" unless="jdk16">...
>
> Comments?

I guess that's tantamount to having source which is at level 1.4 in
the code, but the corresponding javadocs are at level 1.5. Not sure it
is a problem, though. It does add some potential for confusion as to
the source level to the build.xml, so the change should be commented
well. It seems good to be able to use to @code tag:

http://java.sun.com/j2se/1.5.0/docs/guide/javadoc/whatsnew-1.5.0.html

I did the javadoc build on my machine with this change and it
seemed to work.

But I am not familiar enough with the build system to vouch for its
safety.

Dag