DASCA/WALA
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Add Hamcrest dependency

Browse Source 
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.
This commit is contained in:
Ben Liblit 2016-11-29 15:12:54 -06:00
parent 18b79bf0f9
commit cc2dcb91a6
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
com.ibm.wala.core.tests/META-INF/MANIFEST.MF
View File

@ -9,7 +9,8 @@ Require-Bundle: com.ibm.wala.shrike,
org.eclipse.core.runtime,
com.ibm.wala.core.testdata,
org.junit;bundle-version="4.0.0",
org.apache.ant
org.apache.ant,
org.hamcrest.core;bundle-version="1.3.0"
Bundle-Localization: plugin
Export-Package: com.ibm.wala.core.tests.basic,
com.ibm.wala.core.tests.callGraph,