I would have expected the build to fail (via maven-enforcer-plugin?) when
the build is run with a JDK that is not 8.
On Sun, Jul 11, 2021 at 9:30 AM Ralph Goers
wrote:
> Master no longer needs a toolchain file. It only uses Java 11. It sorta
> sounds like you are running with Java 8.
>
> Ralph
>
I’ve been making good progress on the bean stuff. Hopefully untangling the
annotation processor from the annotations and the service class will help
IDE compatibility. As it is, I’ve been running tests from the command line
in individual modules as suggested by Ralph. While not ideal, it’s turned
o
Ah, yes, thank you Ralph, and my mistake: I was not building with Java 11.
Eclipse is still messed up but that's a different story...
Gary
On Sun, Jul 11, 2021 at 3:30 AM Ralph Goers
wrote:
> Master no longer needs a toolchain file. It only uses Java 11. It sorta
> sounds like you are running wi
Master no longer needs a toolchain file. It only uses Java 11. It sorta sounds
like you are running with Java 8.
Ralph
> On Jul 10, 2021, at 1:04 PM, Gary Gregory wrote:
>
> I'm exasperated by our build on the master branch; JPMS feels like the
> iceberg that will sink Java.
>
> I can build r