[ http://issues.apache.org/jira/browse/DERBY-289?page=comments#action_12315860 ]
David Van Couvering commented on DERBY-289: ------------------------------------------- OK. I think we need to solve this. It seems wrong to me to make it so we can't share code across client and server because of, what seems to me anyway, an edge case. I have some ideas, I'm going to do some playing around and prototyping, and I'll get back to you all about this. David > 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
