Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
'Release: update versions for modeshape-5.4.1.Final'

  1. … 70 more files in changeset.
Changed the POMs to 5.5-SNAPSHOT

  1. … 71 more files in changeset.
'Release: update versions for modeshape-5.4.0.Final'

  1. … 70 more files in changeset.
Updates the POM versions to 5.4-SNAPSHOT

  1. … 70 more files in changeset.
'Release: update versions for modeshape-5.3.0.Final'

  1. … 70 more files in changeset.
'Release: update versions for modeshape-4.6.2.Final'

  1. … 62 more files in changeset.
Updates the POM version to 5.3-SNAPSHOT and fixes a minor test issue with the CMIS connector

  1. … 71 more files in changeset.
'Release: update versions for modeshape-5.2.0.Final'

  1. … 70 more files in changeset.
'Release: update versions for modeshape-4.6.1.Final'

  1. … 62 more files in changeset.
Updates the version number to 5.2-SNAPSHOT

  1. … 69 more files in changeset.
'Release: update versions for modeshape-5.1.0.Final'

  1. … 69 more files in changeset.
MODE-2585, MODE-2586 Updates Lucene to 6.0.Final and changes some of the Lucene querying code The following are contained in this commit: a) changing the version to 6.0.Final and making it a private dependency of the lucene-index-provider in WF means we should now be independent of whatever version of Lucene WF/EAP comes with. ModeShape will no longer install Lucene as a first-class dependency in WF. b) with the above change, the ES index provider will use its own separate version (in this case 5.3.1.Final) and from now on can be evolved independently of the lucene-index-provider c) changing the design around the Filter#Results batching mechanism so that index providers can opt for truly lazy index results when SKIP is used. In the case of Lucene this means that the Lucene query is only run once after the first N batches have been skipped. d) changing the logic of the Lucene query making use of BitSets as opposed to loading each document during the collection phase

  1. … 42 more files in changeset.
Changed artifacts version to 5.1-SNAPSHOT

  1. … 64 more files in changeset.
'Release: update versions for modeshape-5.0.0.Final'

  1. … 64 more files in changeset.
Updated the POMs to the next 4.x version.

  1. … 62 more files in changeset.
'Release: update versions for modeshape-4.6.0.Final'

  1. … 62 more files in changeset.
Updates artifact versions to 4.6-SNAPSHOT.

  1. … 66 more files in changeset.
'Release: update versions for modeshape-4.5.0.Final'

  1. … 66 more files in changeset.
MODE-2516 Updates JDK to 1.8 and jboss-parent to the latest version (19) This is the first significant commit of the 5.x series and contains a number of significant changes: - the naming of Maven version properties changed to adopt the standard pattern: 'version.<groupId>.<artifactId>' - build system and dependency updates so that the latest Maven plugin versions function correctly - updating source code to avoid compiler and javadoc warnings

  1. … 154 more files in changeset.
MODE-2159 Validates and fixes various Lucene queries This commit adds extensive unit test support for Lucene queries, reusing most of the tests from the LocalIndexProvider and JcrQueryManager. It fixes the node types change adapter making sure that with each primary type/mixin types change, all the information is sent to the index. It also fixes the "sync reindexing" semantic, making sure that the JcrQueryManger is notified in-thread of any changes.

  1. … 52 more files in changeset.
MODE-2159 Adds the ability to store indexes in Lucene 5. The new Lucene index provider supports all 4 index types: value, enumerated, unique and text. It also supports both single and multi-column indexes, although using multiple columns is likely to have a significant performance penalty because it requires document-merging in Lucene.

  1. … 34 more files in changeset.