Have Jenkins build the V2 stack with Java 6 ?

[Tom Zeller]

>>> Actually, I just went ahead and configured the v2 stack to build with Java 6 in Jenkins.
>>> 
>> Obviously (test failures) I forgot that I’ll need to downgrade Maven on Jenkins for those Java 6 builds. The latest Maven 3.3 requires Java 7.
> 
> I forget, didn't we update the v2 parent POM with newer plugins that require the newer Maven (3.3.x)?  I know we unlocked and switched them all to use parent TRUNK-SNAPSHOT, and thought the plugins and Maven 3.3 were the whole reason for that... If so, then I think that won't work either.

Yes, you’re right. I realized that too shortly after.

> Honestly, if this is going to turn out to be that difficult, I'll restate my original opinion, which is: given the impending EOL and the fact that we literally won't be making any more changes to v2 (except possibly for a security bug), it's probably not worth it to spend a lot of time on this.  I would not personally trouble me if we just kept building it with Java 7, since that's what we've been doing for the last X years.

Yeah, I looked at the IdPv2 wiki space and did not see any statement about a required Java version. Maybe we just need to say 7, but that would change the container requirements etc, but maybe it’s all moot.

TL;DR I’ll revert back to JDK 7 for the builds.