Community
Participate
Working Groups
20030918 see test cases TypeHierarchyTest.testHierarchyWithWorkingCopy1, TypeHierarchyTest.testHierarchyWithWorkingCopy2, TypeHierarchyTest.testHierarchyWithWorkingCopy3 A hierarchy is created on a type that is then opened in an editor. The super type is modified, the editor saved: The type hierarchy does not send a 'typeHierarchyChanged' notification. If I understood correctly, the 'typeHierarchyChanged' is supposed to notify only on save, not while editing the working copy. Crrently it doesn't notify at all.
v20030918 doesn't exist! Could you please provide a test case that uses JDT/Core code only?
Use HEAD of the tests and the test code. the versions denote the jdt.core used, or if its a date, the integration build before that date. I'm afraid I can't rewrite all the test cases to use only jdt.core. Our test project has of course dependencies to jdt.ui and we have valuable test util classes in out plugin. It isn't a bad idea to have our test plugins in the workspace anyways.
Don't worry we have their last integrated instances. However, when entering a defect it isn't a bad idea either to simplify the problem to a test independant scenario. When having to use your HEAD, we usually get into the business of trying to figure how many other things we need to update accordingly, and figure when it is a good time to update... so we will wait until integration has occurred.
We had this discussion a long time ago with SWT. From the overall performance it is more productive to enter a PR without a "component" only test cases. May be it takes us an hour to produce the test case and you know in five minutes what the problem is. But we are always willing to help to reproduce the problem. Moving back to JDT/Core.
Fair enough, but this isn't a 5 minutes operation to get your HEAD contents and grab matching prerequisites, then figure out what your test is meant to achieve. So any early investigation from test owner is guaranteed to speed up considerably the fixing process... avoiding to wait for next integration loop.
Added support to collect changes while the primary working copy is edited, and fire a type hierarchy change on commit.
Verified.
