Patricia Shanahan wrote:
I tried it, and it didn't help. How should I handle jsk-policy.jar in
the jtreg -cpa parameter? Skip it? Point to the ext directory jar file?
If jsk-policy.jar is included in your jre/lib/ext directory, leave it
out of the -cpa parameter list, it will be on the classpath for all
tests. Any classes in the jre extensions directory will be given
preference. I've seen somewhere (from memory) that Window's has two
possible places for jre extensions?
If your getting AccessException's or SecurityException's
jsk-policy.jar's visibility on the classpath will be the problem.
Because of having tried a lot of different things, and more-or-less
random use of JDK 1.5 and 1.6, I tried to do a new check out and
build. Unfortunately, I don't seem to be able to get a clean build.
Can you recommend a version to check out that compiles clean?
954182, my apologies, will fix it soon.
Also, which JDK version should be in the path during the build?
1.6 for the build. 1.5 for the jtreg tests, although you can use 1.6 for
both, some additional tests will fail due to missing keytools, but that
might not be the case for Window's.
From my selfish point of view, the move from make to ant is
unfortunate. As it happens, I've used make since about 1983, and I'm
just learning ant.
Ironic, the motivation for ant was to reduce the barriers for attracting
new developers. I think the barriers are, that distributed programming
is even harder than concurrent programming, so the focus should probably
be on making it easier to debug, your suggestions about handling failure
(favour correctness over trying to continue) make sense to me.
I am less interested in getting the official mechanisms working on
Windows than in getting some combination of scripts that will let me
build and test.
Don't worry we'll get there, I'll have to have another crack at getting
the devel environment set up on Windows too.
Patricia
On 7/17/2010 12:51 AM, Peter Firmstone wrote:
Move the jsk-policy.jar to your jre/lib/ext directory
A number of changes were made recently to make it easier to run the qa
and jtreg tests (at least in a Unix env), previously the qa tests were
run with make and the jtreg tests were run manually and generally this
was done so by Peter Jones from within Sun. There are also some tests
that rely on Sun's internal environment, we need to replicate. We have a
Solaris zone allocated for running a Kerberos Key server but this isn't
complete, we also need to set up a squid proxy.
I made some changes to enable the jtreg tests to be run without
requiring jsk-policy.jar be move to jre/lib/ext/ however this might not
be working on windows.
