| commit | 58e2d3413c97f63259a60885d5f8c59981b5ebe9 | [log] [tgz] |
|---|---|---|
| author | gwt.team.mmendez <gwt.team.mmendez@8db76d5a-ed1c-0410-87a9-c151d255dfc7> | Wed Feb 13 20:54:14 2008 +0000 |
| committer | gwt.team.mmendez <gwt.team.mmendez@8db76d5a-ed1c-0410-87a9-c151d255dfc7> | Wed Feb 13 20:54:14 2008 +0000 |
| tree | b9c1a63f09e30b81ab54f85b8e64e0f4c56eaa24 | |
| parent | 87bfae8689a7eff49226590a1acc139f6592c7d4 [diff] |
We were assuming that JDT's TypeVariableBinding.firstBound would always be a class which may not be true. Based on the JDT 3.1 source this should have always been possible; however people only ran into this problem after we upgraded to JDT 3.3. Review by: spoon git-svn-id: https://google-web-toolkit.googlecode.com/svn/trunk@1850 8db76d5a-ed1c-0410-87a9-c151d255dfc7