Skip to content
This repository was archived by the owner on Feb 26, 2023. It is now read-only.
This repository was archived by the owner on Feb 26, 2023. It is now read-only.

androidannotations.log file constantly grows #1345

Description

@VictorAlbertos

Hi!

I’ve been working with this framework for a while and I've never encountered this problem before:

The "androidannotations.log" file constantly grows,

16

17

and the tasks “:app:assembleDebug” never finishes and the file gets more and more heavy (3 gigas!).

screen shot 2015-03-19 at 15 05 13

I will go to my previous commit -before this mess happened, and see what might be causing this problem.

Any thoughts?

Activity

  1. WonderCsabo commented on Mar 19, 2015

    @WonderCsabo
    Member

    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
    Member

    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
    Author

    Ok, I will focus on finding why "tasks ':app:assembleDebug' never finishes" ;)
    Thanks!

  4. VictorAlbertos commented on Mar 19, 2015

    @VictorAlbertos
    Author

    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
    Member

    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. yDelouis commented on Mar 19, 2015

    @yDelouis
    Contributor

    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.

  7. WonderCsabo commented on Mar 19, 2015

    @WonderCsabo
    Member

    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.

  8. WonderCsabo commented on Mar 22, 2015

    @WonderCsabo
    Member

    @yDelouis WDYT?

  9. yDelouis commented on Mar 23, 2015

    @yDelouis
    Contributor

    I agree.

  10. WonderCsabo commented on Mar 24, 2015

    @WonderCsabo
    Member

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

  11. yDelouis commented on Mar 24, 2015

    @yDelouis
    Contributor

    Ok.

  12. WonderCsabo commented on Apr 20, 2015

    @WonderCsabo
    Member

    I take this over.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions