JITWatch in March/April Java magazine
martijnverburg at gmail.com
Thu Apr 9 09:48:45 UTC 2015
I think the strong advice for those using private APIs is to run the jdeps
tool to see where they are using APIs that will go away / be moved. I'd
then get them to post that list to jigsaw-dev, I guess the root cause of
some of these issues should also be logged in JBS and fixed :-).
On 9 April 2015 at 08:54, Chris Newland <cnewland at chrisnewland.com> wrote:
> Hi all,
> I had an article about the JITWatch AdoptOpenJDK non-Project project
> published in the current edition of Oracle Java magazine:
> The GitHub project now has 489 stars, 11 contributors, and 66 forks.
> On a different subject, there's an interesting discussion just started on
> openjfx-dev about Java 9 which I think is relevant to the Adoption group:
> A few people who are invested in JavaFX seem to be relying on private APIs
> as workarounds for JavaFX bugs or performance issues and were not pleased
> to learn that access to these APIs will disappear with modularisation in
> Java 9.
> Maybe the Adoption group can help with some awareness initiatives and
> start to survey what private APIs are in use to help triage any bugs they
> are working around or any new public APIs that are needed?
More information about the adoption-discuss