Silence the JavacFiler warning 'compiler.warn.proc.unclosed.type.files'

[JessThrysoee]

This prevents warnings like:

warning: Unclosed files for the types '[dummy1407426008266]'; these types will not undergo annotation processing

originating from com.sun.tools.javac.processing.JavacFiler.warnIfUnclosedFiles.

It works by opening and closing an OutputStream on the dummy JavaFileObject,
thereby clearing the dummy filename from the JavacFilers internal openTypeNames set.

Note, this will result in a an empty dummy file, e.g. build/generated/source/apt/debug/dummy1407426008266.java

[JessThrysoee]

I can't reproduce the failure of the Travis CI build locally. Is this a maven-android-plugin issue?

[WonderCsabo]

I never experienced this warning before. What is your platform etc.

[JessThrysoee]

I use androidannotations in Android Studio-0.82 gradle scripts with help from newest android-apt. On OS X 10.9.4.

This warning can be seen in other androidannotations issues:
https://github.com/excilys/androidannotations/search?q=Unclosed+files+for+the+types&ref=cmdform&type=Issues

and a quick google search turns up quite a few hits:
https://www.google.com/search?q=androidannotations+%22Unclosed+files+for+the+types%22

[JessThrysoee]

It was also suggested that an issue should be opened for this: #676 (comment)

[yDelouis]

I confirm the warning using gradle with OSX.

[WonderCsabo]

I am not sure it is the good idea to pollute the generated class folder with these files. What is the source of the issue, maybe a gradle bug?

[JessThrysoee]

I changed the patch so as to avoid creating the dummy file.

Files created via the createResource method are not registered for annotation
processing (as opposed to files created by the createSourceFile method), so we
avoid the JavacFiler warning and we don't have to open/close a stream.

[WonderCsabo]

Nice, i like this way much better.

I do not know what's the problem with the Travis build. Can you please add -e -X flags to the example project build command in the Travis script in a separate branch so we can see more?

[JessThrysoee]

Here is a Travis build with -e -X: https://travis-ci.org/JessThrysoee/androidannotations

The same problem is discussed in these issues:
https://code.google.com/p/maven-android-plugin/issues/detail?id=397
simpligility/android-maven-plugin#415

[WonderCsabo]

I suspect what could be the problem. Travis does not install the build tools SDK component by default anymore. Unfortunetaly i cannot try that out because i am AFK for some time, can you create another PR with exlicitly installing build-tools in the Travis script?

[JessThrysoee]

#1090

[WonderCsabo]

I tested this PR, and i found no regressions with command line maven or with Eclipse. @yDelouis can you try with a gradle project so the root issue is indeed resolved?

[yDelouis]

Tested with gradle on mac. The warning disappeared and the compilation works fine.
Thanks a lot !

[WonderCsabo]

Actually i found out this also happened with maven. At least with maven-compiler-plugin 3.1 with the showWarnings option.

[DayS]

Great job 👍 I was wondering how to resolve this for a while