On Thu, Jul 14, 2016 at 9:10 AM, dalibor topic <dalibor.to...@oracle.com> wrote: > > so it looks like it's getting adopted a little bit faster than log4j 1.x > originally was.
Yes my concern there esp is around the way in which it breaks: subtle change in behavior, not some obvious exception message (such as when someone abuses an internal api). My coworker and I spent half a day tracking down what was happening, and we at least have some knowledge about what to look for. So I just sense some trouble around this stuff for java 9: and some users won't care if its jigsaw or a versioning change or whatever, it just won't work for them. > > With respect to the JDK and the Java community specifically, I think things > have got a bit better then they were a few years ago, thanks to the work > Rory and his collaborators like yourself are doing on raising awareness of > upcoming JDK changes through the Quality Outreach efforts, but as you say, > there is still a long way to go, and we could always use more collaborators. > ;) > I know its super-offtopic but this has been a great change.
