One clarification about the new toolchain feature: The new fork parameter is for when you want to opt-in to using the forked process, but aren't using a toolchain. The toolchain will be picked up automatically without that parameter. I think this might be confusing, so I'm considering <https://github.com/groovy/GMavenPlus/pull/361> just taking that new parameter out.
On Sun, Feb 1, 2026 at 9:19 AM Per Nyfelt <[email protected]> wrote: > Great news! Thanks for this, it will make my life easier :) > On 1/22/26 06:32, Keegan Witt wrote: > > GMavenPlus 4.3.0 <https://github.com/groovy/GMavenPlus/releases/tag/4.3.0> > has been released. This is an exciting release because after years on my > TODO list, I've finally added support for Maven toolchains > <https://maven.apache.org/guides/mini/guide-using-toolchains.html> > (specifically the jdk toolchain). In my testing, this appears to be working > and shouldn't break anything. But please let me know if you find any issues. > -Keegan > > > Bugs > > - Fixed constructor problem (#345 > <https://github.com/groovy/GMavenPlus/pull/345>) (Thanks @cliviu > <https://github.com/cliviu>!) > > Enhancements > > - Support toolchains for compilation, GroovyDoc, and stub generation ( > #349 <https://github.com/groovy/GMavenPlus/pull/349> and #356 > <https://github.com/groovy/GMavenPlus/pull/356>) using the new fork > parameter > > Potentially breaking changes > > None > Notes > > Full Changelog: 4.2.1...4.3.0 > <https://github.com/groovy/GMavenPlus/compare/4.2.1...4.3.0> > > > >
