[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release cnr-data-information-oai-publisher-6.0.0
using released version of dnet-oai-store-service with compression and fixed cache
using oai store service version with compression
[maven-release-plugin] prepare release cnr-data-information-oai-publisher-5.1.0
using version of oai modules that implement the caches
#1342: added caches to limit the load on exists when a client performs a list of getRecord requests.
Not adding AND if we have no query.
[maven-release-plugin] prepare release cnr-data-information-oai-publisher-5.0.2
Setting log of interceptor to debug
[maven-release-plugin] prepare release cnr-data-information-oai-publisher-5.0.1
parent set to released veriosn
depending on snapshot parent
returning the correct error code for non existing identifiers
[maven-release-plugin] prepare release cnr-data-information-oai-publisher-5.0.0
updating to major release of ServiceLocator
[maven-release-plugin] prepare release cnr-data-information-oai-publisher-4.0.0
Preparing for release 4.0.0
Not counting even for date range queries. OAI requests with date ranges are served without the information about the completeListSize.
removed unused properties about OAI
Better to use the info level for the interceptor, so we can see that someone is keeping on harvesting. The possible resumption token is instead printed in debug mode by DNetOAICore
OAI interceptor now logs in debug if everything's ok
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....
log to debug instead of fatal
closing dep ranges
SCRIPT_COMMENT: fixed deploy.info file to the module cnr-data-information-oai-publisher
SCRIPT_COMMENT: Added deploy.info file to the module cnr-data-information-oai-publisher