Community
Participate
Working Groups
3.0 1. compare ContentAssistant rev. 1.36 with tag R2_1 2. in the structured compare viewer select: getContextInformationAutoActivationCharacters(IContentAssistSubjectControl, int); ==> the selection does not cover the selected added element. I would expect that it is at least part of the selected text.
There are more problems than just the subject. In a conflict, if both incoming and outgoing change deleted a method, you can select the deleted method and something random gets selected. If one side contains alphabetized members, and the other doesn't, the selection ranges are very bad. When selecting an incoming addition, the insertion point will be in the middle of an existing javadoc. I'll often see: /** <<ADDITION-------------incoming method on right side * some previous method's javadoc starts here. * ... */ void the method(); The method addition should not be indicated as going into an existing method's javadoc. If there are multiple additions, selecting a single addition will result in a selection range which covers multiple contiguous additions, making it hard to merge the individually.
will anything be happening here for 3.2?
Changes would be major. I don't think to be able to do this for 3.2.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. If the request is still relevant please remove the stalebug whiteboard tag.
