Andrew McIntyre wrote:
So, perhaps a better solution would be to put sysinfo into the client
jar, as we've done with derbynet.jar.
+1
Good for users to be able to run sysinfo in any valid derby configuration.
The issue below brings up an interesting question. The attached diff
for this issue adds derby.jar to the classpath so that the user can
run sysinfo and verify that their classpath is correct. However, a
minimally configured client would only have derbyclient.jar, and I
think we should be promotin
