db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Van Couvering <David.Vancouver...@Sun.COM>
Subject Re: [jira] Commented: (DERBY-289) Enable code sharing between Derby client and engine
Date Thu, 08 Jun 2006 22:46:58 GMT
Hm, it seems a little odd to have Java classes somewhere other than 
under "java".  Doesn't it make it significantly harder to build jar 
files?  Can't the 'clobber' task take care of pruning the 'generated' 


Rick Hillegas (JIRA) wrote:
>     [ http://issues.apache.org/jira/browse/DERBY-289?page=comments#action_12415437 ]

> Rick Hillegas commented on DERBY-289:
> -------------------------------------
> A small refinement:
> I'd like to see the generated files go under a subdirectory parallel to classes and java.
The generated subtree can be wholesale whacked when you clobber your workspace.
>> 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:,,,
>>  Environment: N/A
>>     Reporter: David Van Couvering
>>     Assignee: David Van Couvering
>>     Priority: Minor
>>      Fix For:
>>  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.  

View raw message