Are JBS' policies flexible enough to welcome the JavaFX community?

Robert Krüger krueger at
Mon Apr 20 13:45:19 UTC 2015

On Mon, Apr 20, 2015 at 3:06 PM, Fabrizio Giudici <
Fabrizio.Giudici at> wrote:

> On Mon, 20 Apr 2015 10:55:33 +0200, Mario Torre <neugens at>
> wrote:
>  On Fri, 2015-04-17 at 11:24 +0200, Fabrizio Giudici wrote:
>>> I can't speak in number, because I only have my perspective, and the one
>>> of customers. But comments about workarounds are fundamental to me - let
>>> me add: even the lack of comments about workarounds, because in the end
>>> what one needs is to have his app working
>> But I don't think this is the bug database role, this is for a knowledge
>> base forum.
> I think that bug databases are excellent in this role, indeed it doesn't
> matter a lot the kind of infrastructure, bug tracker or forum. If it's
> HTML, human-readable and googlable, it's ok. In the past I've found myself
> googling around for problems (e.g. with Hibernate) and I got the
> solution... into my own instance of Jira, where years before I've posted a
> problem+workaround about one of my projects, that in the end was related to
> the Hibernate problem. Since the issue was well described, there was the
> workaround I originally applied to my code (which proved to work fine even
> for my more recent need) and the link to the original Hibernate bug, to
> have the details.
>> absolutely. People registered for changes to the respective ticket
automatically get notified when someone posts info about a workaround. This
can be a real life-saver. Separating this into two systems would break
that. It works great for many OSS projects, why should it not for Java?

JavaFX support sources are fragmented enough, which is especially damaging
because the JFX community is still very small. On stackoverflow there are
not many experienced JFX people available, on OTN you also only get trivial
questions answered because obviously the "interesting" people don't go
there and thus people keep posting to openjfx-dev which is absolutely not
the place where this should happen but it is currently the only place where
you find people with profound knowledge on JFX and thus the best source of

More information about the discuss mailing list