Permalink
Switch branches/tags
modeshape-5.4.1.Final modeshape-5.4.0.Final modeshape-5.3.0.Final modeshape-5.2.0.Final modeshape-5.1.0.Final modeshape-5.0.0.Final modeshape-4.6.2.Final modeshape-4.6.1.Final modeshape-4.6.0.Final modeshape-4.5.0.Final modeshape-4.4.0.Final modeshape-4.3.0.Final modeshape-4.2.0.Final modeshape-4.1.0.Final modeshape-4.0.0.Final modeshape-4.0.0.Beta2 modeshape-4.0.0.Beta1 modeshape-4.0.0.Alpha4 modeshape-4.0.0.Alpha3 modeshape-4.0.0.Alpha2 modeshape-4.0.0.Alpha1 modeshape-3.8.1.Final modeshape-3.8.0.Final modeshape-3.7.4.Final modeshape-3.7.3.Final modeshape-3.7.2.Final modeshape-3.7.1.Final modeshape-3.7.0.Final modeshape-3.6.1.Final modeshape-3.6.0.Final modeshape-3.5.0.Final modeshape-3.4.0.Final modeshape-3.3.0.Final modeshape-3.2.0.Final modeshape-3.1.3.Final modeshape-3.1.2.Final modeshape-3.1.1.Final modeshape-3.1.0.Final modeshape-3.0.1.Final modeshape-3.0.0.Final modeshape-3.0.0.CR3 modeshape-3.0.0.CR2 modeshape-3.0.0.CR1 modeshape-3.0.0.Beta4 modeshape-3.0.0.Beta3 modeshape-3.0.0.Beta2 modeshape-3.0.0.Beta1 modeshape-3.0.0.Alpha6 modeshape-3.0.0.Alpha5 modeshape-3.0.0.Alpha4 modeshape-3.0.0.Alpha3 modeshape-3.0.0.Alpha2 modeshape-3.0.0.Alpha1 modeshape-2.8.3.Final modeshape-2.8.2.Final modeshape-2.8.1.GA modeshape-2.8.1.Final modeshape-2.8.0.Final modeshape-2.7.0.Final modeshape-2.6.0.Final modeshape-2.6.0.Beta2 modeshape-2.6.0.Beta1 modeshape-2.5.0.Final modeshape-2.5.0.Beta2 modeshape-2.5.0.Beta1 modeshape-2.4.0.Final modeshape-2.3.0.Final modeshape-2.2.0.Final modeshape-2.1.0.Final modeshape-2.0.0.Final modeshape-1.2.0.Final modeshape-1.1.0.Final modeshape-1.0.0.Final modeshape-1.0.0.Beta1 dna-0.7 dna-0.6 dna-0.5 dna-0.4 dna-0.3 dna-0.2 dna-0.1 EDS_5.3.1_2_2014 3.8.x-prod-ip6.1-ER1
Nothing to show
Commits on Jan 17, 2013
  1. Copied the LICENSE files inside the top-level directory, which is rec…

    …ommended for projects on GitHub.
    rhauch committed Jan 17, 2013
  2. MODE-1750 Ignored two of the TCK tests due to errors in the tests.

    Corrected the link to the JCR project's JIRA in the POM file.
    See MODE-1758 for more detail on the tests and their errors.
    rhauch committed Jan 17, 2013
  3. Removed unused imports

    rhauch committed Jan 17, 2013
  4. MODE-1751 - Updated the algorithm via which nodes update their referr…

    …ers as result to changes in reference properties.
    Horia Chiorean committed with rhauch Jan 17, 2013
  5. MODE-1750 Ignored two of the TCK tests due to errors in the tests.

    See MODE-1758 for more detail on the tests and their errors.
    rhauch committed Jan 17, 2013
Commits on Jan 15, 2013
  1. Updated Arquillian JVM memory setting, increasing the max memory and …

    …permGen size. Without those changes, I cannot run locally the integration tests.
    Horia Chiorean committed with rhauch Jan 15, 2013
  2. MODE-1748 - Fixed the VersionException that was being thrown when con…

    …tent was imported and nodes were marked as checked in. The issue is identical to MODE-1450 and the fix involves propagating a "skipVersioningValidation" flag to avoid the version checks.
    Horia Chiorean committed with rhauch Jan 15, 2013
Commits on Jan 14, 2013
  1. MODE-295: AS7 integration

    okulikov committed with rhauch Jan 10, 2013
  2. MODE-295: Base CMIS library

    okulikov committed with rhauch Jan 7, 2013
  3. MODE-295: Base CMIS library

    okulikov committed with rhauch Jan 7, 2013
  4. MODE-295: Base CMIS library

    okulikov committed with rhauch Jan 7, 2013
  5. MODE-1745 Corrected the names of the child references, which was rece…

    …ntly changed (incorrectly)
    rhauch committed Jan 14, 2013
Commits on Jan 11, 2013
Commits on Jan 10, 2013
  1. MODE-1745 Added repository-level locking to prevent concurrent initia…

    …lization
    
    There were cases when two processes in a cluster would each attempt to
    initialize the system content, and obviously one of them would fail.
    
    This code introduces two new fields to the single 'repository:info'
    document that represents the metadata about the document. There can
    be only one of these in the whole repository. One of the new fields
    is 'intializer' and represents the random UUID of the process that
    is performing the initialization of the repository. Each process
    first looks for this document, and if it doesn't exist the process
    creates a new document with the various metadata fields (including
    the new 'initializer' field) and attempts to 'putIfAbsent'. It then
    looks up the existing document in the store; if the 'initializer'
    field matches its own, then it continues to initialize the repository
    with the system content (e.g., node types, namespaces, etc.),
    initial content, etc. If the document's 'initializer' value does not
    match the current process, then another process is performing the
    initialization and this process should wait until initialization is
    complete. The latter is signified by the other new field, called
    'initializedAt', which is the timestamp that the initializing process
    completed the initialization. Non-initializing processes simply
    block for up to 10 minutes, re-fetching the 'repository:info' document
    and looking for the 'initializedAt' field. As soon as this field is
    found, the non-initializing processes continue.
    
    All of this logic is in the RepositoryCache class. The JcrRepository's
    RunningState.postInitialize() method is what calls the RepositoryCache's
    completeInitialization() method (which uses a transaction to ensure
    the 'intializedAt' field is set atomically).
    
    Note that any process that joins the cluster after the 'repository:info'
    document has been updated with an 'initializedAt' field will immediately
    proceed with starting up (since the repository initialization had
    already been completed).
    
    Also, all processes still attempts to register the node types defined
    within the repository's configuration file. This is obviously redundant
    when each process's configuration file contains the same node types.
    However, this provides a convenient way to register new/updated node
    types by simply starting up another process with an updated list of
    CNDs.
    
    Integration builds pass with these changes, and the test cases
    in MODE-1745 and MODE-1739 run successfully when using these changes
    and Infinispan 5.1.x. There are still issues when run with
    Infinispan 5.2 due to the diff-based delta usage (see MODE-1745
    for details).
    rhauch committed Jan 10, 2013
  2. MODE-1745 MODE-1739 Changed how Delta impls are created

    Recent changes changed the way Delta implementations are created.
    In particular, the SchematicEntryWholeDelta instances were created
    with a clone of the document. Since subsequent changes were made
    to the original document, the SchematicEntryWholeDelta didn't include
    these subsequent changes and they were lost, causing various exceptions.
    
    Also changed some of the trace logging messages on both Delta
    implementations to be more useful.
    
    I'm able to not only successfully run a full integration build,
    but I'm able to successfully run the test cases for both MODE-1745
    and MODE-1739 using Infinispan 5.1.2.FINAL or 5.1.8.Final.
    Occassionally when running the MODE-1739 tests I do get one or two
    NodeNotFoundInParentException (see MODE-1739 for details) early
    on in the test (unable to find a path of an existing node when
    checking permissions), but it simply fails that request and continues.
    This error often happens almost immedidately in the test and is
    rarely repeated more than once.
    
    Note that in addition to this problem, the tests are not able to use
    Infinispan 5.2 -- that's because we're using the SchematicEntryDelta
    (a diff-based impl), and we haven't yet fixed the problem there.
    rhauch committed Jan 10, 2013
  3. MODE-1741 - Updated the Git connector so that indexable branches are …

    …configurable
    Horia Chiorean committed with rhauch Jan 9, 2013
  4. MODE-1741 - Updated Git connector so that only tree/master content is…

    … indexable.
    Horia Chiorean committed with rhauch Jan 7, 2013
  5. MODE-1729 Removed newlines in element values in arquillian.xml

    Not sure why the newlines matter, but they're okay on Windows but
    break the build on OS X.
    rhauch committed Jan 10, 2013
  6. MODE-1745 Corrections to Schematic's state transfer

    Several issues related to state-transfer were identified and corrected within Schematic's DeltaAware implementation. These primarily dealt with using diff-based deltas when using Infinispan 5.2.0 (tested with Beta6 and later), the implementations of the two deltas (and related classes), and how merges are made, and removal of the NullDelta class.
    
    With these changes, the test projects in MODE-1745 and MODE-1746 work better. There still are problems with state transfer during repository initialization. See MODE-1745 for details.
    rhauch committed Jan 10, 2013
  7. MODE-1746 Minor changes to previous modifications

    Several small changes to the previous commit were suggested by Horia,
    and implemented with this commit.
    rhauch committed Jan 10, 2013
Commits on Jan 9, 2013
  1. MODE-1747 Changed default configuration for workspace caches

    Changed the default (built-in) configuration for a repository's in-memory workspace caches (on top of the Infinispan cache used for content) to better work with Infinispan 5.2.
    
    The default can always be overridden in a repository's JSON configuration file.
    rhauch committed with Horia Chiorean Jan 8, 2013