Have Jenkins build the V2 stack with Java 6 ?

[Brent Putman]

On 1/28/16 3:11 PM, Cantor, Scott wrote:
>> 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.
> Consistency alone sort of suggests we do that.

That's true.

>
> Do you want to just re-enable MD5 for now?

I think that's an entirely separate issue, but: Yes, I was going to
suggest we do that also.  I saw that v3 java-opensaml failed on the
OpenJDK builds also, because of the PKIX stuff.  It will take me a
little while to get the test certs fixed up.  I also remembered that
there are also test various CRL's involved, issued by the various root
and intermediate CA's, so I really have to go dredge all that up.

I just updated these files, are there any others?

/opt/jdk1.8.0_72/jre/lib/security/java.security

/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.71-2.b15.el7_2.x86_64/jre/lib/security/java.security

/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.95-2.6.4.0.el7_2.x86_64/jre/lib/security/java.security


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20160128/80bf640b/attachment.html>