Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Message-ID: <703015037.1126139910745.JavaMail.jira@ajax.apache.org>
Date: Thu, 8 Sep 2005 02:38:30 +0200 (CEST)
From: "David Van Couvering (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Assigned: (DERBY-289) Enable code sharing between Derby client
 and engine
In-Reply-To: <1175913042.1116266884833.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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

David Van Couvering reassigned DERBY-289:
-----------------------------------------

    Assign To: David Van Couvering

> Enable code sharing between Derby client and engine
> ---------------------------------------------------
>
>          Key: DERBY-289
>          URL: http://issues.apache.org/jira/browse/DERBY-289
>      Project: Derby
>         Type: Improvement
>   Components: Network Client
>     Versions: 10.0.2.1, 10.0.2.0, 10.0.2.2, 10.1.1.0
>  Environment: N/A
>     Reporter: David Van Couvering
>     Assignee: David Van Couvering
>     Priority: Minor
>      Fix For: 10.2.0.0

>
> Right now, there is no way for the Derby network client to share code with the Derby engine.  We should have a separate jar file, e.g. derby_common.jar, that contains shared code and is used by both the client and the engine.  

-- 
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