androidannotations.log file constantly grows #1345

Activity

1. WonderCsabo commented on Mar 19, 2015

   

   WonderCsabo

   on Mar 19, 2015

   Member

   More actions

   This is the normal behavior. You can reduce the verbosity of the log file or completely disable it (since 3.3). But eventually it will go away at the first project cleaning.
2. WonderCsabo commented on Mar 19, 2015

   

   WonderCsabo

   on Mar 19, 2015

   Member

   More actions

   Sorry, for some reason i skipped this part

   tasks “:app:assembleDebug” never finishes

   This is a problem, it seems the annotation processing made into an infinite loop. Please check your changes, we have to investigate this.
3. VictorAlbertos commented on Mar 19, 2015

   

   VictorAlbertos

   on Mar 19, 2015

   Author

   More actions

   Ok, I will focus on finding why "tasks ':app:assembleDebug' never finishes" ;)
   Thanks!
4. VictorAlbertos commented on Mar 19, 2015

   

   VictorAlbertos

   on Mar 19, 2015

   Author

   More actions

   I’ve found the problem: creating an static class inside an abstract class breaks the annotation processing:

   @EBean
   public abstract class WhoIsTheBug {
   
       @EBean
       public static class ImTheBug {
           public void testMe() {
               Log.d("hello", "hello");
           }
       }
   
   }
   

   Without using enhances annotations, I will instantiate this class like this:

   WhoIsTheBug.ImTheBug instance = new WhoIsTheBug.ImTheBug();
   instance.testMe();

   Do you know why this happens?
5. WonderCsabo commented on Mar 19, 2015

   

   WonderCsabo

   on Mar 19, 2015

   Member

   More actions

   Great, i can repro with Eclipse and gradle, thanks for the minimal example!

   I will debug this. BTW, @yDelouis do you have any idea? I think you worked on inner classes.
6. WonderCsabo

   added

   Defect

   on Mar 19, 2015
7. yDelouis commented on Mar 19, 2015

   

   yDelouis

   on Mar 19, 2015

   Contributor

   More actions

   There is a while loop in the processor for processing enclosing class before the inner class. And the loop stops when everything is generated.
   The problem is that in case of an abstract class, we doesn't generate the subclass, so we never generate the inner class subclass and the loop never stops.

   To fix this, we can generate subclass for abstract classes (which has already been discussed) or prevent inner class in abstract class.
8. WonderCsabo commented on Mar 19, 2015

   

   WonderCsabo

   on Mar 19, 2015

   Member

   More actions

   I see, it makes sense. I do not think we should break the convention of not generating subclasses for abstract classes. I think we should invalidate in this case.
9. WonderCsabo commented on Mar 22, 2015

   

   WonderCsabo

   on Mar 22, 2015

   Member

   More actions

   @yDelouis WDYT?
10. yDelouis commented on Mar 23, 2015

    

    yDelouis

    on Mar 23, 2015

    Contributor

    More actions

    I agree.
11. WonderCsabo commented on Mar 24, 2015

    

    WonderCsabo

    on Mar 24, 2015

    Member

    More actions

    @yDelouis if you do not mind i assigned it to you as you worked on the inner classes generation.
12. WonderCsabo

    assigned

    yDelouis

    on Mar 24, 2015
13. yDelouis commented on Mar 24, 2015

    

    yDelouis

    on Mar 24, 2015

    Contributor

    More actions

    Ok.
14. WonderCsabo commented on Apr 20, 2015

    

    WonderCsabo

    on Apr 20, 2015

    Member

    More actions

    I take this over.
15. WonderCsabo

    assigned

    WonderCsabo

    and unassigned

    yDelouis

    on Apr 20, 2015
16. yDelouis

    closed this as completedin #1371on Apr 25, 2015
17. slandelle

    unassigned

    WonderCsabo

    on Oct 9, 2016