The Bourne shell continuation character is '\' (backslash). as long as there
are no characters after it, except the newline character, this works great.
If somehow a space ends up after the '\', then it is just escaping that space
and the continuation doesn't happen.
Gregg Wonderly
On 11/17/2010 2:49 PM, Tom Hobbs wrote:
Yes, sorry, it looks like I used the wrong continuation character.
Also, I've been running it from the $RIVER_HOME/qa/jtreg directory.
Whether that's the directory you *should* run it from I can't say -
since I can't get it work.
The command does include a "-Djava.protocol.handler.pkgs=net.jini.url"
so maybe I'm just using the wrong method of passing JVM args to jtreg?
On Wed, Nov 17, 2010 at 5:17 PM, Patricia Shanahan<p...@acm.org> wrote:
Given the information about the need to set that parameter, I went back to
trying the long command, but edited to use backslash as end-of-line.
Although Tom's instructions started "cd $RIVER_HOME", I get "Error: Cannot
find file: /home/pats/River/net/jini/url/httpmd/TestEqual.java" unless I run
it from $RIVER_HOME/qa/jtreg. If I run it there, I get "Unexpected
exception: java.net.MalformedURLException: unknown protocol: httpmd".
Tom: Could you clarify the instructions on running the test? Which directory
should I run it in?
Thanks,
Patricia
On 11/17/2010 8:24 AM, Fred Oliver wrote:
In order to find the the httpmd handler, java needs the property
-Djava.protocol.handler.pkgs=net.jini.url
in order to find the handler in the classpath
net.jini.url.httpmd.Handler
I can't speak for jtreg (or how the property gets passed or classpath
issues).
The continuation character should be backslash, shouldn't it?
Fred
On Wed, Nov 17, 2010 at 4:34 AM, Patricia Shanahan<p...@acm.org> wrote:
Pasting the long command into a bash shell just gets me a lot of bash
related errors - I don't think "/" is working as a continuation
character.
Running
jtreg -verbose:all -jdk:"$JAVA_HOME" net/jini/url/httpmd/TestEqual.java
in my qa/jtreg directory does get me the error:
On 11/16/2010 8:12 AM, Tom Hobbs wrote:
I thought that was the case. I just couldn't tell from all the emails
if I'd missed a "I've fixed TestEquals" somewhere in the middle of it.
I ran the specific test by executing the following:
cd $RIVER_HOME
jtreg -verbose:all,nopass /
-cpa:../JTLib-tmp/jsk-lib.jar:/
../JTLib-tmp/jsk-platform.jar:/
../JTLib-tmp/jsk-policy.jar:/
../JTLib-tmp/jsk-resources.jar:/
../JTLib-tmp/phoenix-init.jar /
-jdk:"$JAVA_HOME" /
-Djsk.home="C:\development\projects\River" /
-Djavatest.maxOutputSize=500000 /
-Djava.protocol.handler.pkgs=net.jini.url /
-Djtlib.tmp=../JTLib-tmp /
net/jini/url/httpmd/TestEqual.java
It wouldn't surprise me if me if the command is wrong and that might
explain the problem. I've been putting together this page
http://river.staging.apache.org/building-river.html to help people
with running the tests. I'd appreciate your input.
