[ http://issues.apache.org/jira/browse/DERBY-1424?page=all ]
Andrew McIntyre updated DERBY-1424:
-----------------------------------
Attachment: derby-1424-v1.diff
Attaching a patch for this issue. With the patch I'm seeing some odd behavior
with jdbc4/TestConnectionMethods.java that I'm not sure how it could be related
to my patch, since it only involves Network Server code. But, sure enough, it
passes without the patch and fails with the patch. This test starts the network
server, but then NetworkServerControl.ping() is apparently unable to connect to
the network server. I get errors like:
> INFO: ping returned: java.lang.Exception: DRDA_NoIO.S:Could not connect to
> Derby Network Server on host 127.0.0.1, port 1527.
> FAIL: Failed to start network server
and other communication fails to reach the server as well. I can verfy that the
server has in fact been started. All other tests except
derbynet/testSecMec.java, but that also fails on my machine without the patch,
so I think that's something environmental on my machine.
If anyone has any insight into what might be going on here, or has time to try
out the patch, that would be great. It has turned up several unused classes in
the client, which I'll post about separately on the list.
> 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.
--
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
