Since the datamanger and utilites are not very active, we can use the stable release even though in the trunk.
Change the solr-core to 3.6.2.
Add a dependency on servlet-api.jar with the scope "provided".
Increase the d1 componenets version to 2.3.0 snapshot.
Change it to 2.8.0 version.
Change it to 2.7.0 snapshot.
Change the version of d1_portal to 2.2
Changed the d1_libclient_java from 2.1 to 2.2
bump trunk to 2.6.0-SNAPSHOT and pull in d1 dependencies at 2.1.0-SNAPSHOT to continue trunk development.
use stable EZID 1.0.1 release tag for dependency. https://projects.ecoinformatics.org/ecoinfo/issues/6440
remove d1_annotator and tests from project -- should be used elsewhere.
include d1_annotator dependency
Change the urls of dataone and geotools repositories.
add support for v2 DataONE API.
use maven for datamanager dependency now that EML project has been [partially] maven-ized.
switch to use utilities from Maven repo instead of pulling from SVN and building locally. Added trunk/SNAPSHOT build to dev-testing Hudson (DataONE) for users who do not actively develop the utilities library. Motivated by the HTML->PDF utility, seemed like as good a time as any to convert Metacat's dependency on the project.
Include PDF version of the metadata in the package download. https://projects.ecoinformatics.org/ecoinfo/issues/6053
use newer httpclient library so that Jena's dependency is met - this goes all the way back to d1_common/libclient needing to pull in the newer library.
bump the poms to 2.4.2
switch to ezid 1.0.0 release and pull from dev-testing.dataone.org Maven repo.
Add the dependcy on JBcrypt module.
move metacat trunk to 2.4.0-SNAPSHOT
prep for 2.3.1 release
Add a depency on the commons-jxpath.
use 2.3.0 without SNAPSHOT pre-release.
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),