Community
Participate
Working Groups
I20100429 When an IU is patched and it originally contained a strict negation, the strict negation is not encoded. This is because the code expandRequirementsWithPatches does not encode negation, it does not check for getMax() == 0.
I have released the disabled test case: Bug311330
Note that in this test case the problem of the encoding happens when we are encoding the top level IU (createMustHave).
Created attachment 166876 [details] Simple fix for that bug Here is a simple fix for that bug. It only works when the strict negation is not touched by the patch. To be complete, we should have test cases with: - a patch that introduces a negation - a patch that removes a negation The patch also contains a typo fix in a comment :)
I have released this patch in HEAD. But I'll leave this bug open so we can later deal with the other cases that Daniel mentions in the previous comment.
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. -- The automated Eclipse Genie.
This bug was marked as stalebug a while ago. Marking as wontfix. If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard tag.
