For practical purposes you can treat resolved and closed as the same.
Resolved/fixed versus Closed/fixed does indeed mean what you think, but
the majority of bugs are never verified, so that difference is really
only of interest to the testing organization. I always treat them as the
same in
I see, was not aware that there are enough similarities between 1.x and
later versions. About Resolved issues, I thought that they are waiting for
a fix confirmation to be Closed.
On Mon, Jan 15, 2018 at 5:29 PM, Kevin Rushforth wrote:
> While I suspect many of them
Currently use Arm java8 from Oracle and compile Openjfx for Arm and overlay
libraries for current product line. Looking to test Java9 on Arm and upgrade
product line in next generation release.
Cross Compiling openJdk9 for Arm works fine
Trying to compile openJfx from
Hi Prem,
Since this adds new API, this needs a CSR. In general it is best to get
any proposed API additions reviewed on this alias before spending much
time on it. In this case, the newly proposed API is a simple property,
and is the obvious solution, so the API itself looks fine.
Can you
While I suspect many of them can be closed out at this point, it is not
necessarily a given that they are irrelevant (the scene graph,
animation, and graphics engine evolved from 1.x to 2.0). I agree that it
would be good to take a pass over them and close out the ones that are
no longer
Hello,
JBS still has open issues for JavaFX 1 versions and they appear in searches
even though there's nothing to do about them since that version is not
supported anymore. Is it appropriate to close them all? There are also a
lot in Resolved.
- Nir
Hi Kevin, Ajit
Request you to review following fix:
Bug: https://bugs.openjdk.java.net/browse/JDK-8167096
Webrev: http://cr.openjdk.java.net/~pkbalakr/fx/8167096/webrev00/
Regards,
Prem