Jim Moore

Except that there can certainly be a bump in the major version without being any change in the protocol. A prime example would be v3.x and v4.x being protocol compatible...

@akiranmutnuru Did Jeff's questions and explanation make sense?

@akiranmutnuru Did looking at `/crx/de/exportnodetype.jsp` on both machines clarify the issue?

Suspect this is highly related to GH-96 and GH-65

@viveksachdeva Can you please verify @sagarsane's assumption? Hopefully we can just close this.

The clearer logging would certainly be a good thing...

The runtime itself (i.e., JRE 1.8) is better performance and reliability, but that happens as a deployment concern for AEM. This is about taking advantage of the Java 8 language...

One obvious implication that should be made explicit is that it means that once the change is made it will only work on AEM 6.1+ running on JRE 1.8+. Since...

As far as strategy, I'll edit the description with a checklist. :-)

It's far more a design/correctness thing than performance (which is primarily I/O-bound). While a LOT more static analysis isn't going to solve all problems, it certainly helps drive much better...