Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <20757771.1161988398992.JavaMail.root@brutus>
Date: Fri, 27 Oct 2006 15:33:18 -0700 (PDT)
From: "Daniel John Debrunner (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Closed: (DERBY-1930) Move JDBC implementation notes into the
 published javadoc
In-Reply-To: <28898429.1160000540368.JavaMail.root@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DERBY-1930?page=all ]

Daniel John Debrunner closed DERBY-1930.
----------------------------------------

    Resolution: Fixed

> Move JDBC implementation notes into the published javadoc
> ---------------------------------------------------------
>
>                 Key: DERBY-1930
>                 URL: http://issues.apache.org/jira/browse/DERBY-1930
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation, JDBC
>            Reporter: Daniel John Debrunner
>         Assigned To: Daniel John Debrunner
>            Priority: Minor
>             Fix For: 10.3.0.0
>
>         Attachments: derby1930_diff.txt, package-summary.html, package-summary.html
>
>
> The information in Derby's JDBC implementation notes needs to be in the documentation.
> http://db.apache.org/derby/papers/JDBCImplementation.html
> At least one approach is to add it to the published Javadoc in the package.html for org.apache.derby.jdbc.
> This will make it easier for people to update and ensures that users of Derby have the information with a release.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira