Ben Liblit 8cc4daf6a0 Access static fields directly via the classes that declare them ... Previously some of these were accessing such fields through a subclass of the declaring class. That creates an unnecessary extra inter-class dependency lower in the type hierarchy than necessary. Also, suppress this warning in an automated test input where the indirect static accesses are explicitly intentional.		2017-06-07 08:29:23 -07:00
..
.launchConfigurations	Strip execute bits from many non-executable (i.e., non-script) files	2017-02-23 06:10:08 -06:00
.settings	Suppress Eclipse warnings about potentially-static methods	2017-06-07 08:29:23 -07:00
META-INF	update version to 1.4.3-SNAPSHOT	2017-04-19 09:19:09 -07:00
harness-src/com/ibm/wala/cast/js/test	Access static fields directly via the classes that declare them	2017-06-07 08:29:23 -07:00
.classpath	Use consistent Java versions, usually 1.7	2016-11-29 21:29:30 -06:00
.cvsignore	Strip execute bits from many non-executable (i.e., non-script) files	2017-02-23 06:10:08 -06:00
.project	Strip execute bits from many non-executable (i.e., non-script) files	2017-02-23 06:10:08 -06:00
build.properties	Fix warnings about unset javacProjectSettings build entries (#176)	2017-05-04 11:44:32 -07:00
pom.xml	update version to 1.4.3-SNAPSHOT	2017-04-19 09:19:09 -07:00