On Wed, May 11, 2016 at 2:04 PM, Stuart Marks <stuart.ma...@oracle.com> wrote: > This works if you're willing to build once and use the same binary on > different JDK versions. Where you might run into trouble is if you want to > use the same source code and compile it using different JDK versions. Is > this what you're doing? If so, is there a reason you can't use the same > binary on multiple releases? If not, can you explain what you need to do > that causes deprecation warnings?
The problem is again that the library maintainer is not the same as the compiler invoker. A conscientious library maintainer does not stop at ensuring that their own builds are warning free; they want to ensure as much as they can that their users can also do $compiler -Xlint:all -Werror, even with future javac releases and other folks' toolchains. Of course, this is an impossible task; compilers add warnings all the time. But still one tries! JDK maintainers have the rare luxury of targeting only one release at a time.
