The bad news is that I am still getting problems finding classes for
import statements. The good news is that you may have significantly
simplified the problem. Now I only have to learn about jtreg and its
parameters, not jtreg and ant and a build.xml.
It would be a nice confirmation if you could test the command next time
it is convenient to do so. However, the basic issue is that I have a
-cpa parameter that lists .jar files that should contain the packages
the compiler cannot find. That gives me something to investigate.
Patricia
On 7/15/2010 1:29 AM, Peter Firmstone wrote:
To run the tests manually, do the following:
1. Copy the following files to JTlib-tmp; jsk-lib.jar,
jsk-platform.jar, jsk-resources.jar, phoenix-init.jar, jsk-policy.jar
2. Execute the following jtreg command from the trunk directory,
change the paths to suit your environment.
3. $ jtreg -verbose:all,nopass
-cpa:./qa/jtreg/JTlib-tmp/jsk.lib.jar:./qa/jtreg/JTlib-tmp/jsk-platform.jar:./qa/jtreg/JTlib-tmp/jsk-resources.jar:./qa/jtreg/JTlib-tmp/phoenix-init.jar:.jsk-policy.jar
-jdk /usr/jdk/jdk1.5.0_15 -Djsk.home="/opt/src/river/trunk"
-Djava.security.debug=access,failure
-Djavatest.maxOutputSize=500000 -Djtlib.tmp=./qa/jtreg/JTlib-tmp
./qa/jtreg/
not sure if -cpa:./qa/jtreg/JTlib-tmp/* works, feel free to check. -cpa:
stands for class path append.
Don't worry about any test failures, this might be due to the command,
we're just checking if it's an Ant problem.
I can't actually test the command right now because I'm nowhere near my
dev box and putty doesn't allow that many lines in a command.
Cheers,
Peter.
Patricia Shanahan wrote:
I've just tested 1.8.0, which is before the change in question, and it
still fails the same way. However, it is probably worth trying using
1.7.1 just to remove Ant version as an issue.
Patricia
Peter Firmstone wrote:
I'm using ant version 1.7.1
Peter.
Patricia Shanahan wrote:
Is anyone using the latest Ant version to run the River jtreg tests?
I'm asking because of the following comment on the Commons
Developers mailing list:
"Some change in Ant has broken the property handling in the Jelly/Ant
integration. By manually replacing jars in my local repository I found
out that the tests pass with Ant 1.8.0 but fail with 1.8.1.
Given that Ant's property handling has changed dramatically in 1.8.x
and
Ant even marked this as a backwards incompatible change I'm rather
surprised it still works with 1.8.0."
I had not used Ant for a while when I started trying to get involved
in River, so I downloaded the latest.
Patricia
