db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-289) Enable code sharing between Derby client and engine
Date Wed, 13 Jul 2005 03:40:10 GMT
    [ http://issues.apache.org/jira/browse/DERBY-289?page=comments#action_12315662 ] 

Daniel John Debrunner commented on DERBY-289:
---------------------------------------------

I meant either the 10.2 version or the 10.3 version would be loaded, only one. And the code
has to deal with it.
As it being useful, I don't know, but it is supported today because the client jar and the
engine jar are totally independent,
thus you would be removing this option, or enforcing the requirement that within a same JVM
the client and engine must be in sync.
Maybe that's acceptable, but it does need to be discussed or  addressed, not just assume the
client and the engine will be in sync.

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


Mime
View raw message