Shibboleth Developer's Meeting, 2018-12-21
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-01-04. Any reason to deviate from this?
60 to 90 minute call window.
This week's call will use the Zoom system at GU, see ZoomGU for access info.
AGENDA
- CA/tests
- 3.x branch and logging dependencies with Eclipse
- also
Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key IDP-1373
- also
- Java 11 barriers
- Brexit : do we need to do something ?
Attendees:
Brent
Daniel
- Cutting ldaptive release early next year to fix: https://github.com/vt-middleware/ldaptive/issues/144
...
Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key JPAR-102
- For Pin every artifact in a local Maven repository (directory) :
<keymap>groupId:artifactId:version:type:classifier|SHA-1|0xPGPKeyId</keymap>
For example :
<keymap>org.slf4j:slf4j-api:1.5.6:pom:|b79729ffc12292c0ec755db12360486066f6fd34|0x2C7B12F2A511E325</keymap>- avoid regexes
- too hard to programatically figure out Maven dependencies/plugins/reportPlugins etc
- ~20% of artifacts are unsigned
- store in parent POM
Other