Community
Participate
Working Groups
The new (in 3.0) CDOMerger implementations are far more sophisticated than our old AbstractObjectConflictResolver types. The goal is to develop a CDOMergingConflictResolver that leverages the new code.
New API: org.eclipse.emf.cdo.common.revision.delta.CDORevisionDelta.copy() org.eclipse.emf.cdo.common.commit.CDOChangeSetData.copy() org.eclipse.emf.cdo.common.commit.CDOChangeSetData.merge(CDOChangeSetData) org.eclipse.emf.cdo.common.commit.CDOChangeSetDataProvider org.eclipse.emf.cdo.transaction.CDOTransaction.getChangeSetData() New SPI: org.eclipse.emf.spi.cdo.AbstractConflictResolver org.eclipse.emf.spi.cdo.AbstractChangeSetsConflictResolver org.eclipse.emf.spi.cdo.CDOMergingConflictResolver org.eclipse.emf.spi.cdo.CDOChangeSubscriptionAdapter org.eclipse.emf.spi.cdo.CDOSessionInvalidationAggregator
*** Bug 320485 has been marked as a duplicate of this bug. ***
It's not well-tested (just org.eclipse.emf.cdo.tests.ConflictResolverTest.testCDOMergingConflictResolver) but it seems to work basically. Committed to HEAD
*** Bug 256492 has been marked as a duplicate of this bug. ***
Available in R20110608-1407