On Wed, 17 Nov 2021 at 11:55, Giles Winstanley wrote:
> W.r.t. voting on dev-list, I'm unsure if my use-case is sufficiently
> robust as a NB test to warrant a counting vote,
Only members of the NetBeans PMC have a counting vote. It's the
picking up of problems / regressions before we get to vot
Excellent, thanks Neil, I may go grab that later and see how it goes.
W.r.t. voting on dev-list, I'm unsure if my use-case is sufficiently
robust as a NB test to warrant a counting vote, as I really don't rely
on much of its feature set day-to-day, but I'll see how it goes and make
a choice :)
On Wed, 17 Nov 2021 at 08:18, Giles Winstanley wrote:
> I use Gradle 7.3 as my build system, and the main hiccup I've encountered is
> that NB tooling uses Gradle 7.0 under the hood, which isn't yet JDK17
> compatible (related to bytecode manipulation in underlying Groovy version).
> If you enc
I use Gradle 7.3 as my build system, and the main hiccup I've
encountered is that NB tooling uses Gradle 7.0 under the hood, which
isn't yet JDK17 compatible (related to bytecode manipulation in
underlying Groovy version). If you encounter this NB will raise heaps of
errors and fail you. I can'
If you start from a ZIP distribution, you can launch using any Java version
with your own Java installs e.g. the BAT setup I use when on Windows:
cd %NB_HOME%\bin
start netbeans64.exe --jdkhome %JAVA_HOME% --userdir %NB_USER_DIR% --cachedir
%NB_CACHE_DIR% --console suppress
My various _HOME env
