I think it might work if you replace the path separator colon with a
semicolon ":" with ";"
use -cpa;
Peter.
Patricia Shanahan wrote:
I tried replacing the reference to the jtreg script with:
java -jar c:/apache/jtreg/lib/jtreg.jar
but it made no difference.
Patricia
On 7/15/2010 9:24 PM, Patricia Shanahan wrote:
The list of packages that are not being found is:
com.sun.jini.action
com.sun.jini.config
com.sun.jini.jeri.internal.runtime
com.sun.jini.thread
net.jini.activation
net.jini.config
net.jini.config.AbstractConfiguration
net.jini.constraint
net.jini.constraint.BasicMethodConstraints
net.jini.core.constraint
net.jini.export
net.jini.id
net.jini.iiop
net.jini.io
net.jini.io.context
net.jini.jeri
net.jini.jeri.ServerEndpoint
net.jini.jeri.connection
net.jini.jeri.http
net.jini.jeri.kerberos
net.jini.jeri.ssl
net.jini.jeri.tcp
net.jini.jrmp
net.jini.loader
net.jini.loader.pref
net.jini.security
net.jini.security.policy
net.jini.security.proxytrust
net.jini.url.httpmd
I know e.g. com.sun.jini.thread belongs in sun-util.jar, so I tried
copying that to the temporary library directory and adding it to the
-cpa parameter. It makes no difference. It appears the -cpa is either in
an incorrect format for the Windows version of jtreg, or is otherwise
ineffective.
Here is my current script:
c:/apache/jtreg/win32/bin/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:./qa/jtreg/JTlib-tmp/sun-util.jar"
-jdk "c:/Program Files/Java/jdk1.6.0_20"
-Djsk.home="c:/apache/river/jtsk/trunk"
-Djava.security.debug=access,failure -Djavatest.maxOutputSize=500000
-Djtlib.tmp=./qa/jtreg/JTlib-tmp ./qa/jtreg/
Patricia
On 7/15/2010 5:33 PM, Peter Firmstone wrote:
Hmm, jtreg is designed to be run on all platforms supporting Java, we
should be able to get to the bottom of the problem quickly then. I can
test the command tomorrow.
Cheers,
Peter.
Patricia Shanahan wrote:
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
