> The concern I raised was on making it hard to fix a module because we > introduce multiple changes > > - Java 8 → Java 11, Java 17 > - Linux → Linux, Windows > > That will make it more difficult to get the module building again. I am > not _that_ worried about Windows, I am more thinking about the need to > update the parent POM to >= 35 for Java 11, which brings the migration to > bnd and to the official OSGi annotations.
what would be your proposal to make this less painful? add java 11 and java 17 builds but not remove java 8 builds yet, so it's easier to detect in the different Jenkins builds results that it's still fine with java 8; and remove the java 8 build later? stefan
