Community
Participate
Working Groups
Build Identifier: 4.0 When doing a change to an object (which was already known to the view), which has been updated by a branch-merge change (change on a different branch and merged back to main), you will get an 'attempt to modify historical version' exception on commit. This is caused by the targetGoalDelta (introduced for bug #319522) in the RevisionDelta received for the merge change, having the same version as the source when receiving it from a branch-merge change. Reproducible: Always Steps to Reproduce: 1. Setup 2 transactions, create an element in transaction1 and commit, touch the element in transaction2 (to load it into the view). 2. Setup another branch and do a change to the element on the branch, then merge and commit to normal branch (using transaction1). 3. do another change to the element in transaction2 and commit.
Created attachment 178306 [details] TestCase
Created attachment 178307 [details] Proposed patch Here is a patch proposal, but I'm unsure if this is the correct place to patch. I first tried to patch it on the server, but then went back to patch the version in the InvalidationTransition where the version is usually increased. I increase the version by one when the source version equals the target version, which shouldn't be valid case.
1) The number of lines that you changed is smaller than 250. confirmed. 2) You are the only author of these changed lines. confirmed. 3) You apply the EPL to these changed lines. confirmed.
Good catch, Pascal!
Committed to HEAD
Available in R20110608-1407
