I have such inheritance hierarchy:
A -> B -> C (both A and B are abstract activities/fragments).
All classes have methods with @AfterViews annotations - lets say initA, initB and initC

What I have noticed, if I just compile project (I'm using AndroidStudio, but as I remember I had similar problem in Eclipse), after changing something in class B, methods will be called in order:
initB, initA, initC
After clean rebuild i get the correct order:
initA, initB, initC - until I change again something in B

I think they should always be called in order consistent with inheritance hierarchy, otherwise it causes lots of unexpected bugs if i forget to do clean rebuild