include also the lower and upper bounds in the queries
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] copy for tag cnr-mongo-mdstore-6.0.4
[maven-release-plugin] prepare release cnr-mongo-mdstore-6.0.4
Fixed transaction commit for _id
[maven-release-plugin] copy for tag cnr-mongo-mdstore-6.0.3
[maven-release-plugin] prepare release cnr-mongo-mdstore-6.0.3
Make a copy of the object
[maven-release-plugin] copy for tag cnr-mongo-mdstore-6.0.2
[maven-release-plugin] prepare release cnr-mongo-mdstore-6.0.2
Found bug of missing timestamp. When completing an incremental transaction, the whole record must be copied, not only the id ad body field.
trying to understand why datestamp disappears on mongo
[maven-release-plugin] copy for tag cnr-mongo-mdstore-6.0.1
[maven-release-plugin] prepare release cnr-mongo-mdstore-6.0.1
use released parent
long, not string!
depending on SNAPSHOT parent
use the same (hopefully) format for field timestamp, and the same value for each record involved in a transaction
logging query
using commons-lang3, using lambdas
[maven-release-plugin] copy for tag cnr-mongo-mdstore-6.0.0
[maven-release-plugin] prepare release cnr-mongo-mdstore-6.0.0
fixed test
integrated latest changes from dnet40
depending on releasess
Stroing in mdstore fails if the VTD Parser cannot properly apply the xpaths on records to index
migrated to dnet45
migrated to dnet45, using updated quartz version
codebase used to migrate to java8 the production system