Hey Gordon and Davin,
I think Gordon's comment around the client release is very pertinent,
though checking through an earlier mail from Davin he says:
"
I'm very interested in the REST API for the C++ broker and I've got
git-svn-id:https://svn.apache.org/repos/asf/qpid/trunk@155854913f79535-47bb-0310-9956-ffa450edef68
checked out. I went into the
qpid/java directory and ran:
"
Looking through that in a browser that does contain the Java Broker and
Client stuff as far as I can see, so doing "ant" in the "qpid/java/"
directory *should* build both.
My current best guess is still that the QPID_HOME environment variable
hasn't been set, though clearly it'll make sense for Davin to actually
check which jars have been build and put into "qpid/src/java/build/lib"
Frase
On 17/01/14 09:49, Gordon Sim wrote:
On 01/17/2014 02:34 AM, Shearer, Davin wrote:
Hi Frase,
So still no dice. What jar file has javax.jms.* (like
javax.jms.Connection)?
geronimo-jms_1.1_spec-1.0.jar
I put qpid-all.jar in my CLASSPATH, failed, then
explicitly added all the jar files in qpid/src/java/build/lib:
export CLASSPATH=$(for j in
/home/davin/external/qpid/src/java/build/lib/*.jar; do echo -n
"$j:";done)
and failed again.
The java broker I was using was from the latest release archive. It was
already built for me.
You need the *client* release, or else you can use the build directory
from a source build (which includes both client and broker).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
