Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
Date: Sun, 17 Feb 2008 14:49:22 +0100
From: Kristian Waagan <Kristian.Waagan@Sun.COM>
Subject: Re: a couple of javadoc warnings on trunk
In-reply-to: <47B71BF0.1050007@sbcglobal.net>
Sender: Kristian.Waagan@Sun.COM
To: derby-dev@db.apache.org
Message-id: <47B83B62.5090904@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
References: <47B71BF0.1050007@sbcglobal.net>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)

Hi Kathey,

These warnings were my work, and I hope I have fixed them with revision 
628482 (patch attached to DERBY-1318).
Thanks for letting me know.

While fixing the problems, I noticed a few other things:
 * When I run "java -jar derbyTesting.jar", Java reports that the jar is 
invalid or corrupt.
   With (most of) the other jars, I'm correctly told that there is no 
main class defined.
   I tried with the jars in 10.3.2.1 as well, and observed the same there.
 * There are some build.xml files that cannot be run individually, for 
instance the one for
   impl/services and the one I just changed. I think the reason is 
because java15compile.classpath
   is not set when you run them individually (set as part of a target in 
the root build file).

I just mention the issues in case someone wants to spend some time on them.


-- 
Kristian

Kathey Marsden wrote:
>
>       [javadoc] javadoc: warning - No source files for package 
> org.apache.derbyTesting.functionTests.testData.serializedDataSources
>           [javadoc] 
> C:\nightlies\main\src\opensource\java\testing\org\apache\derbyTesting\functionTests\tests\jdbcapi\DataSourceSerializationTest.java:175: 
> warning - Tag @link: reference not found: java.sql.DataSource
>           [javadoc] 2 warnings
>
>
>