|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
OK, this is fixed now. You can try it out using branch JGRP-1451.
I still have to handle the case where none of the members whose merge solicitations we get are coordinators, e.g.:
A: C,B,A
B: A,D,B
C: A,C
D: B,D
In this case, determineActualMergeCoords() would return an empty list, and Merger.merge() would return with an error message.
However, this is a PATHETIC case, and I'm not sure I even want to handle it ! Starting a new member (e.g. E with view E) would immediately fix it, as E is a real coordinator and would initiate a merge.