Cosmo Sharing Server 0.2
                           Frequently Asked Questions


   Copyright 2005 Open Source Applications Foundation

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.


BUILDING
========

Q: Wow, the build seems to be downloading a lot of jars. Is that
   normal?

    A: Yes. Cosmo has a lot of external dependencies. The jars only need
       to be downloaded the first time you build though, and
       afterwards only when we update our dependencies.

Q: Where did all those downloaded jars go?

    A: In your Maven repository at ~/.maven/repository.

Q: Didn't I download all those jars once before?

    A: Yes, but in 0.2 we have switched from Ant (with the Maven 2.0
       download management tools for Ant) to Maven 1.0. The repository
       formats are different, and so we have to set up a new one the
       first time we build Cosmo.

Q: The build fails because Maven can't download one of my jars. What's
   going on?

    A: A few of our dependencies are not distributed by ibiblio
      (jta.jar is not indepently distributable, and the
      jcr/jackrabbit/jcr-server jars are built from source). OSAF
      hosts a Maven repository containing all of the dependencies. You
      should make sure your project.properties file contains this:

        maven.repo.remote=http://downloads.osafoundation.org/maven/

      and that it is not overridden in your build.properties file.


DEPLOYMENT
==========

Q: Why are you using an RDBMS anyway?

    A: Because it was the easiest way to get up and running. We will
       migrate user and role info to JCR very soon (likely in
       0.3). This will simplify every stage of the process.


$Id$