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 Fri, 09 Jun 2006 01:58:23 GMT
Hm, very interesting.  I think this might be feasible, and I like your 
approach, it keeps all the cruft out of the development environment and 
in the build process.  Let me think about this some more...

David

Kathey Marsden wrote:
> David Van Couvering wrote:
> 
>>   Kathey.  When you say the "code is copied and modified as needed" 
>> what exactly are you thinking of here.  Is this byte-code 
>> modification, or are you proposing a source-code copy/modify.  If the 
>> latter, wouldn't this require also modifying all classes depending 
>> upon the shared classes to use the new package name?
>>
> Sorry, missed this one.  Yes I am talking about a source code modify and 
> yes some tool would have to modify at least  all the  source that 
> imports shared classes and copy all the source over  to production/java  
> to be built to production/classes and then put into the jars.  This 
> would only need to happen once before the final derbyall run and 
> checkin.  During normal development  you can point to the classes and 
> not be impacted.
> 
> I had originally proposed this step just be an alternate build target 
> for nightly and release builds, so developers would not be affected at 
> all, but Dan brought up the good point that develoepers should be 
> building and testing with what we release.
> 
> Kathey
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 

Mime
View raw message