When I pushed updates to my github netbeans fork which triggers the CI
processing as part of
Apache Netbeans Continuous Integration Apache Netbeans Continuous
Integration #12
I get the following issue. Assume this has to do with the
availability/reliability of the osuosl download server. Is the
Other than running performance within Netbeans, is there a way for the
Netbeans code base test suites to be used to run and generate performance
metric reports based on the testing. The results can be published in some
form of build report and identify possible performance bottlenecks in the
code
I tried fresh beta 3 installation with JDK 11 and it works for me. But
when I imported settings from a previous installation (lot of open
projects in my case) for the first time I had to wait for the first
JShell initialization for a long time (maybe there is some
interference with project scannin
