...
Unable to attend
Primarily
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key IDP-2069 Use the recommended setting from https://shibboleth.atlassian.net/wiki/spaces/DEV/pages/1122271670/Configuring+Eclipse#Recommended-Configuration and on a sub project by sub project basis remove all the red (errors) and take a preliminary pass at the yellow (warning)
Not spending much/any time on test code right now
Making notes in the case of any oddities I encounter or leitmotifs (
Instant.now()is an example of ‘I know it’s non null but eclipse doesn’t’Currently up to cas-impl
Scott
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JSPROF-1 RelyingPartyResolverService reimplemented to be CriteriaSet-based and is outside IdP
Removed “hide the ServiceableComponent API” abstraction, may revisit same issue for metadata, access control
Working on ProfileConfiguration cleanup, moving “most” API usage to interfaces, may move all the concrete classes back out of API
SP and IdP overlap is not that extensive here but will share what little there is
Tentatively not planning to produce shareable SAML 1 interfaces at this time
Tom
Jenkins
Created jobs for :
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key GEN-319 Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key GEN-321
Updated Linux and Windows AMIs
When should we start using Maven 3.9.0 ?
...