Hi Peter No real bug, it is a known limitation under Windows it seems... Security related probably...
Best Jonathan 2009/11/9 Peter Firmstone <[email protected]> > Hi Jonathan, > > No worries, I've got the same problem, day jobs that is. > > Well there's really no reason to change it, you've got it sorted already, > the /ext is no longer required for tests. I'll update the docs. Sounds > like a Windows bug, we can just keep using the jre/lib/ext directory on > Windows for now. > > Cheers, > > Peter. > > > Jonathan Costers wrote: > >> Hi Peter >> >> Sorry for not being around lately .. Have been a bit busy with day jobs. >> >> For the QA tests, we can actually work around this by using the >> java.ext.dirs property. >> If you look at the execution part for the QA tests in qa/build.xml, you >> will >> see this property is being set there. >> >> However, setting this property does not work on Windows I've noticed. But >> it >> does on Unix-like platforms, which is enough to get the QA tests working >> under Hudson. >> My initial reason for using java.ext.dirs property was to be able to run >> the >> QA tests under Hudson (since we can't rely on any JARs copied to the >> Hudson >> JVM jre/lib/ext directory). Same is true for jtreg tests I believe. >> >> Best regards >> Jonathan >> >> >> 2009/11/9 Peter Firmstone <[email protected]> >> >> >> >>> Jonathan, >>> >>> Do you think we should create a temporary library directory for >>> jsk-policy.jar similar to what I've done with the jtreg tests so the qa >>> test >>> frame work doesn't require the jre/lib/ext/ directory? >>> >>> I'm happy to leave it alone for the release for now though. >>> >>> Cheers, >>> >>> Peter. >>> >>> >>> >> >> >> > >
