On 04/04/14 13:30, Rob Godfrey wrote:
No... "install in the local repo" is what the mvn clean install will
do... So, you literally just have to follow Robbie's instructions:
check out the qpid-parent-pom/trunk directory, run mvn clean install
from wherever you checked it out to... then go back to the broker and
the maven build should complete ok. Hope this helps, Rob
Cheers Rob,
I ended up figuring out that myself after staring at the instructions
for a while and deciding that I was reading way too much into things :-)
I've now got the Java Broker etc. built using Maven but before I play
with the QMF things I wouldn't mind answers to a few Maven questions -
I'm still very much at the "Burn the Witch" stage wrt. my trust of Maven ;-)
I've now ended up with a directory
/home/fadams/.m2/repository
Filled with stuff.
I'm not clear by what witchcraft Maven decides what to shove there - for
example I eyeballed the parent pom.xml and saw the dependencies, but
when I looked at the repository after running mvn clean install on that
I was kind of expecting the directories in the repository to pretty much
match what was in the dependencies, but it definitely didn't after
running mvn on the parent pom.xml, though to be fair after building the
main things it does all appear to match (though with a ton of other
stuff too).
When I build the Java Broker etc. it seemed to take an age, when I was
using ant it took under a minute on my system, but with Maven it reports
a total time of 5:18 min and it looks like it was downloading half the
Internet :-D I'm *guessing* that this is a one-off cost as it fills up
my local repo with stuff?
Where do you set CLASSPATH when you build using Maven? With the ant
build I used to have:
<qpid>qpid/java/build/lib/qpid-all.jar
Which was nice and convenient, if possibly a bit sloppy, from what I can
see each qpid/java subdirectory seems to have a target directory e.g.
qpid/java/client/target though in there there is
qpid-client-0.28-SNAPSHOT.jar which seems less convenient that
qpid-client.jar if I want to set up CLASSPATH in my .bashrc. Am I
missing something?
Another thing that I'm not clear on is that in the Maven repository
there seems to be a bunch of jars installed - as an example
org/eclipse/jetty/jetty-websocket/8.1.14.v20131031/jetty-websocket-8.1.14.v20131031.jar.
In the "olden days" Qpid pulled in jetty and the Jar was available in
qpid/java/build/lib so when I was messing around with Jetty on another
project I had it handily on my CLASSPATH - I can't seem to see jetty
anywhere now except in the Maven repository? So how does the Broker see it?
In the olden days when I just did "ant" at the end of that I ended up
with something that would run 'cause I had
<qpid-trunk>qpid/java/build/bin
on my path and could simply do "qpid-server" but now there's no nice
convenient build directory.
I noticed in
qpid/java/broker/target/qpid-broker-0.28-SNAPSHOT-bin.tar.gz that
archive seems to contain qpid-server, do I *really* have to now have to
faff around copying and unpacking archives everytime I want to update a
build? That seems an awful lot less convenient than simply doing "ant
clean" then "ant".
Have I missed something? I hope so 'cause if not it seems a step
backwards from a "just works" POV
This might all be second nature to folks familiar with Maven, but I'm a
bit "old skool" and I quite like knowing what's installed on my system,
where it is installed, and why it's there so I'd quite like a bit of
reassurance :-)
Frase
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
