Shibboleth Developer's Meeting, 2020-06-05

Brent

Daniel

Henri

Ian

• Thread safety is hard:
  • Arises through 

    Jira Legacy
    server Shibboleth JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 180d847f-bce4-36b2-9964-771bff586829 key MDA-242

    Full ; full discussion there.
  • TL;DR: A lot of things we say are @ThreadSafe really aren't, although they are mostly @ThreadSafeAfterInit and other things probably conspire to mean we're probably OK , mostlyin practice. This makes me uncomfortable.
  • It's not possible even in principle to make most things truly @ThreadSafe because of 

    Jira Legacy
    server Shibboleth JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 180d847f-bce4-36b2-9964-771bff586829 key JSPT-97

    .
  • We could fix that (and I think we should) but that wouldn't address all the issues, just make it possible to do so for cases we care most about.
  • Beyond that, I don't think really nailing this down is going to be felt to be worthwhile, but we might want to document some assumptions and possibly tweak a couple of base classes in java-support to future-proof them.change some annotations anyway.
• Building from Docker containers: iay/shibboleth-build-docker seems to work

Marvin

Rod

• Built VM soley to do windows installer builds
• What to do about Java7/8 on Windows and the multi tests?

...