Benjamin Marwell

[BUILD] update build to require Java 11+ for building

23

replace `maven.compiler.source` and `maven.compiler.target` with `maven.compiler.release` (still pointing to 8), which brings better API checks, Javadoc linting, compilation performance, etc. PR inc

[#228] build with Java 11

2

Fixes #228 This PR shows that Java 9+ methods were already used and the Java 8 bytecode uses Java 9+ APIs. This can be fixed by using Multi-Release-JARs. I think...

Surefire [INFO] output lines do not get prefixed with module name in batch mode

3

# how to reproduce start a multi-module project with `mvnd --batch-mode verify` # what to expect module names get prefixed for every line # what actually happens those lines from...

## **⚠️ This PR requires a vote** Please do not merge unless the vote has passed. The vote shall only be on the used Java version, not on the properties...

[#282] fork parameter

15

Fixes #282 This PR allows building with an external `groovyc` compiler. Currently, the only option is to use the `groovyc` from either `${GROOVY_HOME}/bin` or `${PATH}` (in that order), just like...

[#286] disable SecurityManager starting with Java 21

7

fixes #286

The security Manager is deprecated for removal since Java 17. In Java 21, it is a no-op and t he warning cannot be removed anymore. Therefore, remove the Security Manager...

`verbose` is unused and should be deprecated for removal. Not to soon, obviously. Or just leave it in as a no-op in case groovyc supports it some day… Source: https://issues.apache.org/jira/browse/GROOVY-11194

Just a reminder for me. Currently, the CI does `clean install invoker:install invoker:test`. Preferrably, all a user would need to do is `mvn verify`. Install will also clutter the user's...

Create a `fork` option to prepare toolchain support

1

Before we implement toolchains, I suggest to implement a `fork` parameter first. Rationale: * Forking is needed for toolchains anyway, as `groovyc` will be called * Toolchains without forking might...