db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew McIntyre (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1424) Build derbyclient.jar from a dependency list generated by classlister
Date Sat, 17 Jun 2006 00:01:30 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1424?page=all ]

Andrew McIntyre updated DERBY-1424:

    Attachment: derbyclient_classlister.patch

Attaching a patch for this issue. I haven't had time to thoroughly test it yet due to trouble
with the testing environment where I was working on this, but I wanted to make sure I didn't
lose the patch since I had already put it together.

> Build derbyclient.jar from a dependency list generated by classlister
> ---------------------------------------------------------------------
>          Key: DERBY-1424
>          URL: http://issues.apache.org/jira/browse/DERBY-1424
>      Project: Derby
>         Type: Improvement

>   Components: Build tools
>     Versions:
>     Reporter: Andrew McIntyre
>     Assignee: Andrew McIntyre
>      Fix For:
>  Attachments: 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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message