On Tue, Nov 1, 2011 at 7:01 AM, Jimmi Dyson <[email protected]>wrote:
> Hi there, > > I've been really impressed with how easy PAX Exam has been to use to > create integration tests for OSGi bundles, but I've hit upon a bug that I > can't seem to figure out. It could be a bug in the JVM, but I'd really > appreciate your input to see if it's a known problem with any workaround. > > We experienced the same issue using PAX Exam 1 so I thought I'd try out > PAX Exam 2 (which I must say is definitley a step in the right direction), > but the issue still occurs. This very well could be environmental so any > pointers would be appreciated. > > On my dev laptop, 64 bit JDK 1.6.0_26, everything works fine. When this > gets built on a Jenkins slave, using 32 bit JDK 1.6.0_17-b04, we get the > following failure: > Do you have to use 1.6.0_17? It has some pretty large security issues (e.g., http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-3865).
_______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
