summaryrefslogtreecommitdiffstats
path: root/.settings
diff options
context:
space:
mode:
authorDavid Pursehouse <david.pursehouse@sonymobile.com>2014-10-31 11:24:52 +0900
committerDavid Pursehouse <david.pursehouse@sonymobile.com>2014-10-31 08:27:01 +0000
commit41abb376ca443387e747e50549109ee80052b589 (patch)
treeda302a5598003b95f1989ee04a516a34b4de0aa1 /.settings
parent51e708c464f37d8e7df38805052a9bff369751a3 (diff)
Enable and fix Eclipse warnings about redundant type arguments
Since Java 7 it is possible to replace the type arguments required to invoke the constructor of a generic class with an empty set of type parameters (<>) as long as the compiler can infer the type arguments from the context [1]. Enable the Eclipse warning about redundant type arguments, and remove the ones it warns about. [1] http://goo.gl/SG21kM Change-Id: I422882949a6a6a57391580d881f73120b2843a0e
Diffstat (limited to '.settings')
-rw-r--r--.settings/org.eclipse.jdt.core.prefs2
1 files changed, 1 insertions, 1 deletions
diff --git a/.settings/org.eclipse.jdt.core.prefs b/.settings/org.eclipse.jdt.core.prefs
index aae063214a..3cc353b428 100644
--- a/.settings/org.eclipse.jdt.core.prefs
+++ b/.settings/org.eclipse.jdt.core.prefs
@@ -54,7 +54,7 @@ org.eclipse.jdt.core.compiler.problem.potentiallyUnclosedCloseable=ignore
org.eclipse.jdt.core.compiler.problem.rawTypeReference=warning
org.eclipse.jdt.core.compiler.problem.redundantNullAnnotation=warning
org.eclipse.jdt.core.compiler.problem.redundantNullCheck=ignore
-org.eclipse.jdt.core.compiler.problem.redundantSpecificationOfTypeArguments=ignore
+org.eclipse.jdt.core.compiler.problem.redundantSpecificationOfTypeArguments=warning
org.eclipse.jdt.core.compiler.problem.redundantSuperinterface=ignore
org.eclipse.jdt.core.compiler.problem.reportMethodCanBePotentiallyStatic=ignore
org.eclipse.jdt.core.compiler.problem.reportMethodCanBeStatic=ignore