[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release dnet-oai-utils-3.3.2
revert dependency: I work=ngly updated misc-utils insteaad of cql-utils
depending on cnr-cql-uils [2,3)
[maven-release-plugin] prepare release dnet-oai-utils-3.3.0
reverted to revision 38450
[maven-release-plugin] prepare release dnet-oai-utils-5.0.0
Created new version of oai-store that stores record compressed on mongo
[maven-release-plugin] prepare release dnet-oai-utils-3.2.0
bumped version
#1342: added caches to limit the load on exists when a client performs a list of getRecord requests.
[maven-release-plugin] prepare release dnet-oai-utils-3.1.2
[maven-release-plugin] prepare release dnet-oai-utils-3.1.1
[maven-release-plugin] prepare release dnet-oai-utils-3.1.0
RecordInfo with provenance.
[maven-release-plugin] prepare release dnet-oai-utils-3.0.0
updating to major release of ServiceLocator
[maven-release-plugin] prepare release dnet-oai-utils-2.1.0
Added SCM
Preparing for release 2.1.0
Using releases for basic D-Net modules
The oai database currently in use is discovered dynamically from the OAIConfiguration profile.The xquery to use to retrieve the db name from the configuration is in the property services.oai.publisher.db.xquery.The OAI controller/core have been refactored....
No hadoop-parent: classes needed in mapreduce-jobs have been copied to avoid the jar to inherit "heavy dependencies" to spring and dnet IS.
need dnet-hadoop-parent because imported by dnet-mapreduce-jobs. Added <relativePath/> to avoid build warning.
closing dep ranges.