NullPointerException #378

Activity

1. pyricau commented on Nov 5, 2012

   

   pyricau

   on Nov 5, 2012

   Contributor

   More actions

   Hello @Bersh ! Thank you for reporting this error.

   I checked ModelExtractor:

       private Set<DeclaredType> buildAnnotationTypes() {
           Set<DeclaredType> annotationTypesToCheck = new HashSet<DeclaredType>();
           for (Class<? extends Annotation> annotation : lookupAnnotations) {
               TypeElement typeElement = processingEnv.getElementUtils().getTypeElement(annotation.getName());
               annotationTypesToCheck.add((DeclaredType) typeElement.asType());
           }
           return annotationTypesToCheck;
       }

   Here is appears that typeElement is null.

   This means that processingEnv.getElementUtils().getTypeElement(annotation.getName()) returns null. The javadoc of getTypeElement() states that it returns the named type element, or null if it cannot be found.

   From this we can deduce that at least one of the annotations could not be found in the classpath of the processor. lookupAnnotations is the list of annotations supported by AndroidAnnotations, so those should be in the annotation processor classpath.

   I see that you are using AndroidAnnotation 2.7. Are you using 2.7-SNAPSHOT, or the 2.7 stable release (released yesterday night) ?

   So my next question is : are you using Maven (and if yes, could you paste the dependencies configuration block for AndroidAnnotations), or the bundled zip ?
2. Bersh commented on Nov 5, 2012

   

   Bersh

   on Nov 5, 2012

   Author

   More actions

   I'm using 2.7-SNAPSHOT. Sorry, it seems that it was just some broken version in my local maven repository. After removing androidannotations from repo and downloading it again everything is ok. Or maybe this bug may was alrady fixed
3. pyricau commented on Nov 5, 2012

   

   pyricau

   on Nov 5, 2012

   Contributor

   More actions

   I think the problem may be that the androidannotations-api.jar wasn't updated at the same time the androidannotations.jar was. So the annotation processor expected some new annotations but couldn't find them on the classpath because androidannotations-api.jar didn't contain them.

   Thank you anyway !
4. pyricau

   closed this as completedon Nov 5, 2012