The CI builds at https://builds.apache.org/job/POI/ run with JDK 6 and don't run into this failure:
>> Using Java: 1.6.0_27/1.6.0_27-b07/20.2-b06/Java HotSpot(TM) 64-Bit Server VM >> from Sun Microsystems Inc. on Windows Server 2008: 6.0 I have now also created a separate build which uses OpenJDK at https://builds.apache.org/view/POI/job/POI-OpenJDK/, the build is still running, let's see if the same happens there. Dominik. On Wed, Nov 5, 2014 at 12:03 AM, Andreas Beeker <[email protected]> wrote: > On 04.11.2014 20:33, Nick Burch wrote: >> Maybe add a catch for it, and log a "your jvm is broken, consider updating" >> in place of the current failure? >> >> That'd let me roll the 3.11 beta 3 release :) >> > > I preferred to add a workaround to use BouncyCastle in this case. > Btw. I usually have the latest JDK 6 as my development/testing jre, so > Windows seems not to be affected. > I hope the hashing algorithms are not subject to jce policy limitations - > at least I couldn't find something under > http://docs.oracle.com/javase/7/docs/technotes/guides/security/SunProviders.html > > Andi. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
