Hi
Do we have a bytecode enforcer rule but for plugins?
That would help users who are eventually stuck with Java 8 and so cannot
upgrade plugins going to be 11 required.
Cheers
Olivier
On Tue, 14 Nov 2023 at 5:38 am, Karl Heinz Marbaise
wrote:
> Hi,
>
> currently we have already the build re
+1
To discuss what versions matrix we want to have in CI builds ... lts +
latest-ea? so will be 11, 17, 21, 22
I also build legacy applications with target 8 by jdk 11+ and don't see any
issue.
pon., 13 lis 2023 o 20:38 Karl Heinz Marbaise
napisał(a):
> Hi,
>
> currently we have already the
+1
Sylwester
Ps. Hope to see soon that we drop Java 8 completely
pon., 13 lis 2023, 20:38 użytkownik Karl Heinz Marbaise
napisał:
> Hi,
>
> currently we have already the build requirements for Maven Core at JDK11+
>
> So in consequence I would suggest to lift the minimum requirement for
> buil
Big +1
I sometimes need to switch back from JDK 21 to 17 or earlier to build
some of the plugins.
If we start building with 11+, we can detect build errors easier for newer JDKs.
The spotless profile might not be the only profile we can remove.
One catch, though. Should we not test on JDK8? Maybe
Hi,
currently we have already the build requirements for Maven Core at JDK11+
So in consequence I would suggest to lift the minimum requirement for
building plugins to JDK11.
That means also we can use "--release 8" option
(8) instead of
source/target which is not correct based on the warnings
