This is the mail archive of the java-patches@gcc.gnu.org mailing list for the Java project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [patch] minimal test case for sha-1 and md5


Casey Marshall wrote:

PR libgcj/17903:
* testsuite/libjava.lang/md5test.java: New file.
* testsuite/libjava.lang/md5test.out: Likewise.
* testsuite/libjava.lang/shatest.java: Likewise.
* testsuite/libjava.lang/shatest.out: Likewise.

Hi Andreas, These tests fail for me because I run the testsuite without installing the built GCJ: -------------------------- 8< -------------------------- WARNING: could not properly read security provider files: file:///home/ranmath/gcc/lib/security/libgcj.security file:///home/ranmath/gcc/lib/security/classpath.security Falling back to standard GNU security provider -------------------------- 8< --------------------------


I seem to recall there being a mini flamewar about that message,
anyway: that java.security.Security prints messages to System.err if
it can't find any security properties file to load.

I think we are wrong to print that message, since nothing else in the
library does that, to my knowledge. Anyway, it's obnoxious, the
situation it describes just means a default was used, and it looks
more like debug cruft than anything else.

A nicer solution than following Sun's single-buttock'd way of doing
this would be to allow provider implementations to include this
information in Jar/.so files, like how JAXP does with
MEAT-INF/services.

Any votes for removing that message?

I vote for removing in standard output. Maybe we can keep it within a DEBUG output ?
This would make my life a bit easier :)


Andreas


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]