DASCA
/
WALA
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
WALA/com.ibm.wala.scandroid/.settings/org.eclipse.jdt.core.prefs

10 lines
507 B
Plaintext
Raw Normal View History

scandriod merge
2014-10-02 01:32:36 +00:00
eclipse.preferences.version=1
Ignore missing non-null-by-default annotations in Eclipse In general, the WALA code base is not really ready for nullness checking. It would be nice if we got there some day, but I'm not planning to take that on now or any time soon. Until then, it's not useful to warn about missing @NonNullByDefault declarations on WALA packages. See also older commit 7b6811b.
2016-11-06 17:41:38 +00:00
org.eclipse.jdt.core.compiler.annotation.missingNonNullByDefaultAnnotation=ignore
scandriod merge
2014-10-02 01:32:36 +00:00
org.eclipse.jdt.core.compiler.codegen.inlineJsrBytecode=enabled
org.eclipse.jdt.core.compiler.codegen.targetPlatform=1.7
org.eclipse.jdt.core.compiler.compliance=1.7
org.eclipse.jdt.core.compiler.problem.assertIdentifier=error
org.eclipse.jdt.core.compiler.problem.enumIdentifier=error
Ignore potential null accesses in Eclipse Eclipse Mars Service Release 2 finds 45 potential null pointer accesses across WALA's various Eclipse projects. Eclipse ignores these by default, but any individual user may have changed their personal Eclipse configuration to treat them as warnings or errors. Thus, some people will find that the code builds while others find that it fails. Better to explicitly use a known-good configuration. In the long run someone should inspect these cases one-by-one and fix them where appropriate. But that is probably better managed as part of a larger effort to tidy up nulls in WALA. I'm not planning to take that on now or any time soon, though, so this is a better setup for now.
2016-06-27 17:46:55 +00:00
org.eclipse.jdt.core.compiler.problem.potentialNullReference=ignore
scandriod merge
2014-10-02 01:32:36 +00:00
org.eclipse.jdt.core.compiler.source=1.7