Test for IDSCHEME and IDNAMESPACE
Fixed xqueries and methods to get the id namespace and scheme.
[maven-release-plugin] prepare for next development iteration
[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
Not counting even for date range queries. OAI requests with date ranges are served without the information about the completeListSize.
Using releases for basic D-Net modules
idScheme and idNamespace are not a property anymore, but they are dynamically read from the OAI configuration profile
Cleaned logs
Allow "<>" in queries in OAI configuration using EscapeXML before saving to the configuration profile.
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.
remove definition of SplittedQueryExecutor bean, now defined in cnr-service-common instead. Changed resource annotation to autowired
SCRIPT_COMMENT: fixed deploy.info file to the module dnet-oai-utils
SCRIPT_COMMENT: Added deploy.info file to the module dnet-oai-utils