You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 26, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Feb 26, 2023. It is now read-only.
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.
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.
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.
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,
and the tasks “:app:assembleDebug” never finishes and the file gets more and more heavy (3 gigas!).
I will go to my previous commit -before this mess happened, and see what might be causing this problem.
Any thoughts?