Have Jenkins build the V2 stack with Java 6 ?

[Cantor, Scott]

On 1/27/16, 12:31 PM, "dev on behalf of Tom Zeller" <dev-bounces at shibboleth.net on behalf of tzeller at dragonacea.biz> wrote:



>Soon to be a moot point, but I think we need to either (a) build the v2 stack with Java 6 or (b) add -bootclasspath[1] to the parent POM(s). A little bit of searching yields the opinion that (a) is easier because otherwise the path to the “old” JDK needs to be hardcoded into POMs.

I don't think we've ever used (b). I was under the impression Brent said he had put out some of the earlier stuff built with Java 7, but I might be misremembering.

On the few occasions I did some V2 releases, I did use Java 6 even after the EOL. Just wanted to eliminate any inconsistencies across our releases.

>We build the v3 stack with Oracle’s Java 7, FYI. I was wondering what exactly we would need to do to build the v3 stack using Java 8, and it looks like we should stick with 7.

I think that was our plan for the moment at least.

>My questions is : should I go through the effort of getting Java 6 on shibboleth.net for the Jenkins builds, or ignore ? It’s not a big deal to do so.

Brent's call I think.

-- Scott

>