Some source files here definitely use Hamcrest, so listing it as a dependency seems reasonable. What I find confusing is the inconsistency among my Eclipse installations. On some of my various machines, Eclipse reports an error if this dependency is not listed. On others, Eclipse finds the required jar and reports no error, even if this dependency is not listed. I don't know why the latter works, or why the inconsistency exists at all. Eclipse is a complex, subtle beast. What I can say is that this change fixes the error for my Eclipses that were reporting an error, and does not introduce any new errors for my Eclipses that were already happy before this change. |
||
---|---|---|
.. | ||
.settings | ||
META-INF | ||
dat | ||
launchers | ||
src/com/ibm/wala | ||
.classpath | ||
.project | ||
build.properties | ||
build.xml | ||
javaCompiler...args | ||
plugin.properties | ||
plugin.xml | ||
pom.xml |