[ http://issues.apache.org/jira/browse/DERBY-289?page=comments#action_12315870 ]
Rick Hillegas commented on DERBY-289: ------------------------------------- I confess I'm still puzzled. It seems to me there may be two separate issues here: 1) the interoperability of different derby versions across a network and 2) the coherence of derby code running in a single VM. I'm all in favor of interoperability. But mixing and matching derby versions in the same VM puzzles me. I wonder whether we are talking about an edge case here. Is that edge case worth not sharing utility libraries across derby? > 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
