use 2.3.0 for this next release of metacat.
make sure all versions are using 2.2.2 of some sort -- thinking of making this release a 2.3.0 release because we will be branching/tagging from the trunk, not the 2.2.x branch.
1.Remved the dependency on solr-core since the metacat-common alreay has the dependency.2.Excluded the slf4j-log jar files since we are using slf4j-log4j jar file.
prep for 2.2.0 release. include configuration value for metacatui deployment context.
Change the verson of the metacat-common to be the 2.2.0-SNAPSHOT.
[merge from branch to keep trunk up to date with upgrade history] prep for Metacat 2.1.1 release
use v2.1.0 for all metacat release components for consistency
remove all -SNAPSHOT artifacts in favor of released versions in preparation for Metacat v2.1.0 release
use tagged/released version of d1-portal project. https://projects.ecoinformatics.org/ecoinfo/issues/5936
First pass at MN.getPackage() implementation using Bagit library from LOC. https://projects.ecoinformatics.org/ecoinfo/issues/6026
first pass at integrating CILogon/MyProxy certificates in Metacat. Configuration is specific to mn-demo-4.test.dataone.org for the time being (this will cause localhost deployments to fail webapp deployment). https://projects.ecoinformatics.org/ecoinfo/issues/5936
exclude jibx-tools, maven cruft and org.eclipse "dependencies" to cut down on the number of jar files in the lib folder.
move to libclient/common snapshot to match metacat-common project.
force the use of newer xercesImpl 2.7.1
Add the dependency to the metacat-common.
use maven to manage most jar dependencies in Metacat.Exceptions include: LSID, Datamamager (EML),