db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Trejkaz (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-289) Enable code sharing between Derby client and engine
Date Sun, 07 Feb 2016 23:25:39 GMT

    [ https://issues.apache.org/jira/browse/DERBY-289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15136517#comment-15136517

Trejkaz commented on DERBY-289:

We tried to use Elasticsearch in an application which happens to also have both derby.jar
and derbyclient.jar on the classpath. Elasticsearch fires up its "JarHell" utility when you
start up a node, which basically scans the entire classpath looking for jars which contain
the same class files, and then bombs out when it notices that derby.jar and derbyclient.jar
contain class files with the same path.

So even though this is just an "improvement"... it is kind of a pain for us now.

> Enable code sharing between Derby client and engine
> ---------------------------------------------------
>                 Key: DERBY-289
>                 URL: https://issues.apache.org/jira/browse/DERBY-289
>             Project: Derby
>          Issue Type: Improvement
>          Components: Network Client
>    Affects Versions:,,,
>         Environment: N/A
>            Reporter: David Van Couvering
>            Priority: Minor
>         Attachments: DERBY-289.diff
> 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 was sent by Atlassian JIRA

View raw message