[ http://issues.apache.org/jira/browse/DERBY-289?page=comments#action_12319103 ]
Kathey Marsden commented on DERBY-289: -------------------------------------- David Van Couvering wrote: >I'm uncomfortable with the "build trick" -- it feels like a hack. Let's >think about this some more. > I agree. I don't like either one of my ideas much to tell you the truth and stick by original assessment of hard and weird respecively. I threw them out there in the hopes that someone would counter with something better #:). Satheesh's sealed jar idea sounds much more promising to me if it pans out. If not, maybe others have some good ideas on how to share code and still allow version mixing of the jar files. > 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
