cosmo and snarf maven tweaks

i've just made a series of commits that tweak the maven
build and
deploy processes for osaf-commons-jackrabbit, cosmo,
cosmo-migrate and
snarf. specifically:

 * osaf-commons-jackrabbit uses the 'org.osaf.commons'
groupId
 * cosmo and cosmo-migrate use the 'org.osaf.cosmo'
groupId
 * snarf uses the 'org.osaf.server' groupId

osaf-commons-jackrabbit is updated to version 0.5, including
the
latest jackrabbit build.

snarf now includes the cosmo-migrate jar in the
$OSAFSRV_HOME/lib
distro directory. any other dependencies with type 'app'
will also be
included in that directory. this allows one to run the cosmo
migration
tool with the following command:

  $ java -jar
$OSAFSRV_HOME/lib/cosmo-migrate-0.3-SNAPSHOT.jar
[options...]

ps: in case anybody's curious, here's how you deploy the
various artifacts:

  osaf-commons-jackrabbit: 'maven
plugin:repository-deploy'
  cosmo: 'maven war:deploy'
  cosmo-migrate: 'maven javaapp:deploy'

snarf doesn't have a deploy target because we don't
currently put it
in our maven repo.
_______________________________________________
cosmo-dev mailing list
cosmo-devlists.osafoundation.org
http://lists.osafoundation.org/mailman/listinfo/cosmo-d
ev