aboutsummaryrefslogtreecommitdiff
path: root/pom.xml
diff options
context:
space:
mode:
authorThomas Broyer <t.broyer@ltgt.net>2015-07-10 16:56:40 +0200
committerThomas Broyer <t.broyer@ltgt.net>2015-07-10 16:56:40 +0200
commit5a37c2aa596377cb4c9b6f916614407fd0a7d3db (patch)
tree607b58ef666766742d9537062432dcdf2f53146a /pom.xml
parentdfa195e79e03f5e9846be8c475eb61b687de7ef5 (diff)
downloadjavapoet-5a37c2aa596377cb4c9b6f916614407fd0a7d3db.tar.gz
Workaround for Eclipse JDT/APT bug around intersection types
When in presence of a TypeVariable with an intersection type as the upper bound, Eclipse JDT/APT returns a TypeVariable equivalent to the declaring TypeVariable when calling getUpperBound. The only way to retrieve the actual bounds is to go look at the TypeParameterElement represented by the TypeVariable.
Diffstat (limited to 'pom.xml')
-rw-r--r--pom.xml6
1 files changed, 6 insertions, 0 deletions
diff --git a/pom.xml b/pom.xml
index 99ef785..fc73432 100644
--- a/pom.xml
+++ b/pom.xml
@@ -81,6 +81,12 @@
<version>1.10.16</version>
<scope>test</scope>
</dependency>
+ <dependency>
+ <groupId>org.eclipse.jdt.core.compiler</groupId>
+ <artifactId>ecj</artifactId>
+ <version>4.4.2</version>
+ <scope>test</scope>
+ </dependency>
</dependencies>
<build>