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] Resolved: (DERBY-1424) Build derbyclient.jar from a dependency list generated by classlister
Date Fri, 04 Aug 2006 21:35:41 GMT
Great, thanks!

Andrew McIntyre (JIRA) wrote:
>      [ http://issues.apache.org/jira/browse/DERBY-1424?page=all ]
> 
> Andrew McIntyre resolved DERBY-1424.
> ------------------------------------
> 
>     Resolution: Fixed
> 
> Committed to trunk with revision 428891.
> 
>> Build derbyclient.jar from a dependency list generated by classlister
>> ---------------------------------------------------------------------
>>
>>                 Key: DERBY-1424
>>                 URL: http://issues.apache.org/jira/browse/DERBY-1424
>>             Project: Derby
>>          Issue Type: Improvement
>>          Components: Build tools
>>    Affects Versions: 10.2.0.0
>>            Reporter: Andrew McIntyre
>>         Assigned To: Andrew McIntyre
>>             Fix For: 10.2.0.0
>>
>>         Attachments: derby-1424-v1.diff, derbyclient_classlister.patch
>>
>>
>> Currently, derbyclient.jar is built from a hardcoded list of classes in the top-level
build.xml file. This causes a few unnecessary and unwanted classfiles to be added to the insane
jar files, such as SanityManager and some of the reference files. derbyclient.jar should be
built from a dependency list generated by classlister, similar to how the other jars are built.
> 

Mime
View raw message