bcm at osafoundation.org
Wed Feb 1 12:52:18 PST 2006
On 1/31/06, Heikki Toivonen <heikki at osafoundation.org> wrote:
> Brian Moseley wrote:
> > i think there must be ;) no additional scripts or copyying wars around
> > are required for anything. you simply:
> Ok, I think I have figured out part of my confusion. Where there used to
> be a single wiki page I needed to go to figure out how to build and run
> Cosmo, there are now 3 pages I need to go to get and build all the
> pieces I need (and I assume at least the cosmo build page is a little
> out of date):
> I guess I must have glossed over at some detail without understanding
> what it really meant.
thanks for pointing this out. the new cosmo build docs are not done
yet, because i got pulled off of the build reorg to work on 0.2.7
(which i need to talk about in another email).
i did update the cosmo build instructions to 1) link to the new
JavaServerSetup page that explains how to set up your system for java
development (at least for the osaf server projects) and 2) note that
they are only good for the 0.2 branch.
0.3 build instructions are coming as soon as 0.2.7 is out the door.
> By the way, are all of these maven commands needed, or are there
> dependencies such that any missing steps will be done by other commands?
> maven build
> maven dist
> maven war:inplace
build is an alias for war:webapp. war:webapp is a prereq of
war:inplace. so usually you will never need to do build (or
war:webapp) at all.
dist does it all - builds (via war:webapp) and tests (via test:test).
however, it has been superseded by war:inplace. in 0.2, we use dist to
set up and configure a tomcat instance with cosmo in it. in 0.3, once
you've run war:inplace, you go over to snarf and dist *that* to build
a tomcat instance. you then just need to point the tomcat instance at
your dev cosmo webapp that was built by war:inplace.
does that make sense? is there an easier way for me to explain it?
> (Btw, I finally managed to get it up and running, so there is hope;)
> I think the step 3. on
> could use a little clarification. First it was not clear to me how I
> could tell which Context element to edit. Also, I found that if you are
there are three contexts - ROOT (which is just a welcome page for the
integrated server, accessed at http://<host>/), /scooby and /cosmo.
change the docBase of the /cosmo one.
> on Windows, and even if you run Cygwin, you must give the path as
> Windows path (found that out by looking at snarf.log).
yeah pathing under cygwin has never been straightforward to me. this
is a good bit to know.
> So, now that I have it running, I found out that the scripts in
> cosmo/hammer won't work because the path to cosmo changed (was /, now
> /cosmo) for your server running with default settings on localhost. Any
> other tests that assume cosmo is at / are also broken. I guess all tests
> need a new command line option to set the path on the server (or to make
> it simpler, change them to take a URL instead).
url is a better choice than host and port. feel free to make that change :)
> Anyway, thanks for all the help and clarifications. I should be able to
> proceed again.
great. keep asking questions. this is all fodder for the build
instructions and faq :)
More information about the Cosmo