...
Just working on 2 outstanding Santuario issues for release:
Jira Legacy server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key OSJ-315 Jira Legacy server System JIRA columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key OSJ-344
...
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
Dependencies with no (r(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.
...