...
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 5.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, 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.
John
Marvin
Phil
Helping Henri to finalise some of the commons metadata cache stuff, including:
A new factory to help simplify the config
A super simple cache implementation for the admin flow.
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JOIDCRP-11 Resolve a client_id for the downstream OP (issuer) from a simple map
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JOIDCRP-12 Build client authentication from parameters resolved from a storage service - just a map in an XML config file for now.
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JCOMOIDC-40 Implemented the string version. Need to look at the others.
Rod
m2 checking on by default
Is this the correct default?
-P central-disabled
is no more
java-mvn-enforcer releases
-data 1.0.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.
...