Thanks, I'll take a look. On Fri, Nov 27, 2015 at 12:31 PM <[email protected]> wrote:
> I found that this bug is causing lint exceptions in 24.5.0 whenever trying > to resolve a class that was declared in a dependent Java project: > > at > org.eclipse.jdt.internal.compiler.problem.ProblemHandler.handle(ProblemHandler.java:152) > at > org.eclipse.jdt.internal.compiler.problem.ProblemHandler.handle(ProblemHandler.java:217) > at > org.eclipse.jdt.internal.compiler.problem.ProblemReporter.handle(ProblemReporter.java:2364) > at > org.eclipse.jdt.internal.compiler.problem.ProblemReporter.isClassPathCorrect(ProblemReporter.java:4684) > at > org.eclipse.jdt.internal.compiler.lookup.UnresolvedReferenceBinding.resolve(UnresolvedReferenceBinding.java:104) > at > org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.resolveType(BinaryTypeBinding.java:182) > at > org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.superclass(BinaryTypeBinding.java:1768) > at > com.android.tools.lint.EcjParser.findSuperMethodBinding(EcjParser.java:880) > at com.android.tools.lint.EcjParser.access$1000(EcjParser.java:132) > at > com.android.tools.lint.EcjParser$EcjResolvedMethod.getAnnotations(EcjParser.java:1188) > at > com.android.tools.lint.checks.SupportAnnotationDetector$CallVisitor.checkCall(SupportAnnotationDetector.java:1603) > at > com.android.tools.lint.checks.SupportAnnotationDetector$CallVisitor.visitConstructorInvocation(SupportAnnotationDetector.java:1585) > > I updated the ticket with this callstack. > > On Friday, November 13, 2015 at 9:26:13 AM UTC-8, [email protected] > wrote: >> >> This looks pretty much like a bug, so I filed an issue about it: >> https://code.google.com/p/android/issues/detail?id=194092. >> >> On Monday, November 9, 2015 at 3:17:41 PM UTC-8, [email protected] >> wrote: >>> >>> Hi, >>> >>> I noticed that Lint seems to miss java project dependencies when setting >>> up the classpath for compilation. In particular, >>> EcjParser.computeClassPath() seems to add the classes from all versioned >>> dependencies (both Java and Android), but only the Android project >>> dependencies. As a result, converting an Android dependency into a regular >>> Java dependency is causing my Lint checks to fail. I verified the behavior >>> in 1.5.0-beta1. Is this a known bug? >>> >>> Thanks, >>> César >>> >> -- > You received this message because you are subscribed to the Google Groups > "adt-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
