[cosmo-dev] IMPORTANT: new webapp packaging
bcm at osafoundation.org
Mon Dec 10 17:41:34 PST 2007
On Dec 10, 2007 4:27 PM, Bobby Rullo <br at osafoundation.org> wrote:
> a) What version of tomcat should we/ can we use for the standalone
5.5.x should work. we're using 5.5.17 for snarf I believe. I've never
tested with 6.
> b) Do we have to copy some jars over to the tomcat common/lib
> directory from somewhere, or should it work as is in a "stock" Tomcat?
yes. if you look at an assembled snarf (run mvn assembly:directory
within the snarf subdir, then look at
dist/osaf-.../osaf-.../tomcat/common/lib), you'll see a bunch of jars
that aren't in your stock Tomcat common/lib. just copy them over.
we were talking about that on IRC earlier. the question is whether we
should put those in the "shipping war" (as opposed to the snarf one)
or if we should list them as dependencies for common/lib. we could
actually ship tarballs for both - one with dependencies, one without,
and let the deployer pick the one that fits his setup best.
you also need to configure logging by dropping a log4j.xml into your
Tomcat's common/classes. again, you can start with the one from the
assembled snarf and go from there.
first thing on my plate tomorrow is to put all this on a wiki page.
> c) "mvn assembly:directory" no longer seems to work. Actually, neither
> does "mvn package" in snarf. The "osaf-server-bundle-0.12-
> SNAPSHOT.tar.gz" file does get created, but there is no WAR file in it
> anywhere. Is there a different command used to build snarf now? I am
> asking because I would like to use the war's context file as the
> template for my own custom one. Brian's is ok, but it doesn't tell me
> how to configure derby, and has other custom bcm stuff.
the one in the assembled war is exactly the same as
cosmo/build/context.xml. remember, when you drop it in
$CATALINA_HOME/conf/Catalina/localhost/, it needs to be named
chandler.xml in order to be mounted at /chandler.
More information about the cosmo-dev