Resources / Runtime tests: Do not depend on higher-level plug-ins.#2161
Resources / Runtime tests: Do not depend on higher-level plug-ins.#2161laeubi merged 2 commits intoeclipse-platform:masterfrom
Conversation
|
This pull request changes some projects for the first time in this development cycle. An additional commit containing all the necessary changes was pushed to the top of this PR's branch. To obtain these changes (for example if you want to push more changes) either fetch from your fork or apply the git patch. Git patchFurther information are available in Common Build Issues - Missing version increments. |
| String MULTI_FILT_ID = "org.eclipse.core.resources.regexFilterMatcher"; | ||
| String FILT_ARG = "foo.*"; |
There was a problem hiding this comment.
I must confess I don't understand what this actually does and where it is needed in the test but would trust your analysis here and it looks much more understandable than the previous version.
There was a problem hiding this comment.
Yeah, the test basically just wants any <filteredResources><filter>... in the .project metadata. And we should use one here that is actually known here (or upstream) :)
* PreferencesServiceTest is not deterministic but its behavior changes depending on the presence of downstream plug-in org.eclipse.core.resources. Take this into account. * IResourceTest should not depend on downstream plug-in org.eclipse.ui.ide (even inside a downstream repository). Use a different (upstream) filter provider in the unit test instead. These downstream plug-ins are currently only visible because Tycho adds the full-blown UI test harness to the target platform unconditionally, even if there is no such actual dependency [1]. This is a cleanup in preparation for [2]. [1] eclipse-tycho/tycho#5349 [2] eclipse-tycho/tycho#5362
58e6c5b to
6b340ef
Compare
PreferencesServiceTest is not deterministic but its behavior changes depending on the presence of downstream plug-in org.eclipse.core.resources. Take this into account.
IResourceTest should not depend on downstream plug-in org.eclipse.ui.ide (even inside a downstream repository). Use a different (upstream) filter provider in the unit test instead.
These downstream plug-ins are currently only visible because Tycho adds the full-blown UI test harness to the target platform unconditionally, even if there is no such actual dependency [1]. This is a cleanup in preparation for [2].
[1] eclipse-tycho/tycho#5349
[2] eclipse-tycho/tycho#5362