Hello,
It is unrelated with Java 11. It has always been the case, but we've now been so long all using Java 8 that most people forgot about this requirement.
IOW, it was already unsupported to, say, run a master on a Java 8 and an agent on Java 7.
This is because the remoting layer of Jenkins serializes classes from master and agents, and hence could trigger very weird behaviors.
This means you could think it's OK, until it's not and you need to fix this immediately (e.g. a plugin started to depend on some particular feature, or does some funky dynamic loading depending on the current JRE, then will send it to the "other side" of the network, and that "other side" will not have all classes available to deserialize).
I would strongly encourage everyone to install the Version Node monitors plugin to watch this out.
(disclaimer: I'm the current official maintainer, but it's also been worked on overall by the Java 11 team).
Note: this does *not* mean you cannot build projects using a JDK 1.4, or 8, or whatever.
We're talking here about the version of Java runtimes to run the Jenkins master instance and its agents.
Hope this clarifies.
-- Baptiste