Scala 2.12 does not support a JDK 11 target

[gsmet]

And in any case, it will need to be -target:11 when we switch to 2.13.

[gsmet]

@famod I'm surprised this change triggered so many native builds?

[famod]

@gsmet I'll have a look later today.

[famod]

Interesting:

[INFO] Scanning for projects...
[INFO] gitflow-incremental-builder 3.14.2 starting...
[INFO] Reference commit of branch HEAD is commit of id: commit 47f2eb37b4d9de6424ca9df56be67849b562455e 1624350667 ------p
[INFO] Reference commit of branch origin/main is commit of id: commit 4450e9e05a914fc46c11d6eb372e5bbb64966bb2 1624350755 ------p
[INFO] Using merge base of id: commit 65e3aa05e088355b014d20b197086eac83ec888d 1624346942 --tr-sp
Warning:  Ignoring changed file in non-reactor module: /home/runner/work/quarkus/quarkus/integration-tests/scala/src/test/resources/projects/classic-scala/pom.xml
[INFO] ------------------------------------------------------------------------
[INFO] No changed artifacts detected: Executing validate goal on current project only, skipping all submodules.
[INFO] gitflow-incremental-builder exiting...

So, no changes have been detected. 🤔 I'll check that warning.

PS: No changes means full build btw. because an empty list of changed modules is considered to be the "GIB disabled" case in CI.

[famod]

I have to take a closer look but I think this is a bug in GIB somewhere here: https://github.com/gitflow-incremental-builder/gitflow-incremental-builder/blob/master/src/main/java/com/vackosar/gitflowincrementalbuild/control/ChangedProjects.java#L47-L48

[gsmet]

I suppose it's because the change was inside a nested Maven project maybe?

[famod]

Yes, I think so. I'll have to take into account src.

[famod]

I have a fix for this. I'll release GIB 3.14.3 in the next few days.