@yDelouis this makes a strange "error" and i do not know why. The problem is that the compile-time tests create an androidannotations.log file in the project folder, which has lots of entries. This file has not been created before this PR.

@yDelouis @DayS i found no fix for the core issue, so this could be interesting.

i think this should be merged. while it is not an actual fix for the core issue, it can be a way to workaround the issue for those having issues with a locked logfile.

also having open PRs that are ready to merge and having no points against a merge feels bad 😜. so either merge or close.

Yes, i do not like dangling PRs as well! Actually i think this feature can be also useful some people for other reasons.

BTW, i just checked the diff and it has syntax highlight now. Awesome! Now i only miss --follow-renames in GitHub, because currently we do not see any history before renames which is very annoying. :)

yeah. might be usefull for other cases to... like disabling the logfile just for the reason that you have not check it ever (like for me^^). i even had to search it in my gradle build directory to find it.

Seems good to me.
May you add a note in the wiki ?

Done.

@yDelouis this has a regression: when running the compile-time tests, the androidannotations.log file is saved to the root of the androidannotations module.