Community
Participate
Working Groups
Unexpected deltas. ----------- Expected ------------ P[*]: {CHILDREN}\n src[*]: {CHILDREN}\n p[*]: {CHILDREN}\n A.java[+]: {} ------------ but was ------------ P[*]: {CHILDREN}\n src[*]: {CHILDREN}\n p[+]: {}\n \n P[*]: {CHILDREN}\n src[*]: {CHILDREN}\n p[*]: {CHILDREN}\n A.java[+]: {} --------- Difference is ---------- expected:<...]: {CHILDREN}\n p[[]*]: {CHILDREN}\n ...> but was:<...]: {CHILDREN}\n p[[+]: {}\n \n P[*]: {CHILDREN}\n src[*]: {CHILDREN}\n p[]*]: {CHILDREN}\n ...> junit.framework.ComparisonFailure: Unexpected deltas. ----------- Expected ------------ P[*]: {CHILDREN}\n src[*]: {CHILDREN}\n p[*]: {CHILDREN}\n A.java[+]: {} ------------ but was ------------ P[*]: {CHILDREN}\n src[*]: {CHILDREN}\n p[+]: {}\n \n P[*]: {CHILDREN}\n src[*]: {CHILDREN}\n p[*]: {CHILDREN}\n A.java[+]: {} --------- Difference is ---------- expected:<...]: {CHILDREN}\n p[[]*]: {CHILDREN}\n ...> but was:<...]: {CHILDREN}\n p[[+]: {}\n \n P[*]: {CHILDREN}\n src[*]: {CHILDREN}\n p[]*]: {CHILDREN}\n ...> at org.eclipse.jdt.core.tests.junit.extension.TestCase.assertStringEquals(TestCase.java:266) at org.eclipse.jdt.core.tests.junit.extension.TestCase.assertEquals(TestCase.java:242) at org.eclipse.jdt.core.tests.model.AbstractJavaModelTests.assertDeltas(AbstractJavaModelTests.java:1233) at org.eclipse.jdt.core.tests.model.AbstractJavaModelTests.assertDeltas(AbstractJavaModelTests.java:1223) at org.eclipse.jdt.core.tests.model.InclusionPatternsTests.testCreateIncludedCompilationUnit(InclusionPatternsTests.java:199)
4.17 RC1? Really?
(In reply to Stephan Herrmann from comment #1) > 4.17 RC1? Really? :( - now beyond 4.16 and 4.17 Bulk move out of 4.17
Bulk move out of 4.19
Bulk move out of 4.20
Bulk Move out of 4.21
Bulk move out of 4.22. If this is going to make it to 4.22, feel free to set the target back.
Bulk move out of 4.23
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.