[ http://issues.apache.org/jira/browse/DERBY-289?page=comments#action_12319068 ]
Satheesh Bandaram commented on DERBY-289: ----------------------------------------- Thanks, Kathey... I think we may be able to use JAR sealing mechanism to enforce consistant version of the classes are used. We already use sealing for the server JAR, so a similar mechanism could work for the client. I haven't actually used sealing yet, so don't know if there are any issues in doing so :) > 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
