...
This week's call will use the Zoom system at GU, see ZoomGU for access info.
AGENDA
Freeze schedule
Freeze Mar 28th to cut beta releases
Tentative release perhaps the following week.
Attendees:
Brent
Just working on 2 outstanding Santuario issues for release:
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key OSJ-315 Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key OSJ-344
Daniel
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key IDP-1917 bug fix for connection pool passivation
Henri
Done:
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JOIDC-78 Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JOIDC-79 Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JOIDC-81
...
Working on a dependency pass for 4.2.
Had held this until the enforcer was up and running.
Ran into some holes in my dependency qualification workflow from that, now reorganised.
May move this into the build containers at some point.
Lost more than a week on a medical issue (I’m fine for now, but it’s time-consuming).
As Tom points out, Maven 53.8.5 is out:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12351105
Doesn’t seem to have anything we actually need. For what it’s worth, though, it seems to perform our builds unchanged and the new dependencies it brings in don’t need any new keys.
Adopting by bumping minimum version would require all dev machines, CI machines and build containers to be updated.
If we do want to make it the minimum for 4.2, we need to start on that stuff NOW. Inclined to make it optional (by ignoring it).
It has some plugin dependency requirements that I will pick up anyway.
Dependencies with new keys (deferred until resolved, working on these with Rod):
rhino, jcommander, janino,
Dependencies with no (recent) keys (I thought this wasn’t supposed to be possible these days):
hibernate
Big bumps (suggest ignoring these):
Mockito (new APIs in major version)
Checkstyle (may do an 8.x update, but both 9.x and 10.x exist now… also, interaction with Eclipse)
Little bumps (still to be pulled in):
Some Maven plugins.
The ones Rod is key hunting for.
Maybe Checkstyle.
JAXB API and runtime versions have split.
Coming back to the 5.x conversion now that Spring Framework 6.0.0-M3 is out. Spring Webflow still the sticking point.
...
m2 checking on by default
Is this the correct default?
-P central-disabledis no more
java-mvn-enforcer releases
-data (two releases)
At least one more data release (when the key thing is sorted).
Need to do an enforcer release before 4.2.
Did the releases from docker with an ssh tunnel.
Are we good to turn off external access?
The bug in maven which required us to turn off checksum checking on our repos has been fixed.
Requires resolver 1.8 (which may not be released yet).
Is it in Maven 53.8.5?
Scott
Finished initial round of OP doc updates
Re-did view changes after last meeting to eliminate some bloat and get more insight into accessibility. Boy, the new HTML tags are interesting (and completely under-spec’d).
Mac’s screen reader is at least usable to get some insight.
No idea why SauceLabs doesn’t like our HTML, I don’t think there’s anything wrong with it and the checkers I tried agree.
Made a lot of additions and alterations to the new OIDC registration access token process
Hit a bunch of consent-related issues this week, some long dormant bugs. Hopefully didn’t break CAS but added a number of fixes there to handle consent better (e.g. it embeds consented IDs like OIDC does so per-session and client-side consent can work).
Don’t see a lot of point trying to do this for SAML and it would only be possible in a subset of configs anyway.
...