2019-02-01
Shibboleth Developer's Meeting, 2019-02-01
Call Administrivia
10:00 Central US / 11:00 Eastern US / 16:00 UK
Calls are normally the 1st and 3rd Fridays of each month. Next call would be Friday 2019-02-15. Any reason to deviate from this?
60 to 90 minute call window.
Call Details
This week's call will use the Zoom system at GU, see ZoomGU for access info.
AGENDA
Transition to Java 11 (iay).
Approve pin-the-stack plan as specified below (Tom)
TLS renegotiation issues if not covered already
Attendees:
Brent
- OSJ-265 - Getting issue details... STATUS
Daniel
Ian
Java 7 platform:
All
-multitests (JPAR, JSPT, JSE, OSJ, IDP, XSTJ, MDA) running clean with Java 7, Java 8, Java 11.What about 12 and 13?
Java 8 platform:
All
-multitests (JPAR, JSPT, JSE, OSJ, IDP, XSTJ, MDA) running clean with Java 8, Java 11.What about 12 and 13?
Java 9 and Java 10:
Removed from all Jenkins
-multijobs for both the Java 7 and Java 8 platform.
Java 11 platform:
Will transition to this from the Java 8 platform once we have everything on the other two platforms testing successfully under Java 11.
Obviously, will drop testing with Java 8.
What about 12 and 13?
Post-java-11:
Nothing scary in Java 12 or Java 13 yet.
Marvin
Rod
- EDS-83 - Getting issue details... STATUS
Continued pulling deprecated stuff from Attribute filter and resolver.
Low hanging fruit / low merge impact changed complete and the is hugely more legible
Moving into the corners
PrincipalAuthn
Idp2 style NameID/NameIdentifier
Now have about 40 checkins queued...
Questions:
Is code coverage a dead thing?
(iay): JaCoCo claims proper support for Java 11, as of a few days ago: https://github.com/jacoco/jacoco/releases/tag/v0.8.3; I would support trying to bring this back but only for the Java 11 / IdP V4 branch.
There was some discussion about being able to always preserve constructor parameter names in > Java7. Do we still care?
Scott
- IDP-1357 - Getting issue details... STATUS
master converted to UnboundID via internal property wiring a la Santuario linefeed fix
- IDP-1405 - Getting issue details... STATUS
This will be a pretty disruptive commit, timing?
Guava really making this more work than it should be, but managing
Significant wiring change needed to replace Functions.compose
Liberally replacing the most minimal anonymous classes with lambdas
Do we care about some of the really simple stuff? (e.g. Predicates.alwaysTrue/False)
Tom
Other