...
Rod Widdowson Philip Smart Site builds (which generate java doc and run weekly) x Nightly builds (which consume javadoc) x version revision == broken nightlys
Maven Central Repository - see my (Tom) section below for details - do we want to :
(a) publish our repo URL in the POM and maintain long-term / forever-ish ? in a profile not activated by default ?
or (b) remove from POM and publish our repo URL in the wiki as documentation for developers to add to ~/.m2/settings.xml ? (that’s my suggestion)
Add items for discussion here
...
Busy elsewhere
OpenSSL3 https://shibboleth.atlassian.net/browse/SSPCPP-946 & testing
Next stage sig checking- work mostly understood. Pending https://shibboleth.atlassian.net/browse/JPAR-195
Questions about https://shibboleth.atlassian.net/browse/IDP-1874 & https://shibboleth.atlassian.net/browse/IDP-1877
Scott
Tom
Maven Central :
Looks like we will not publish artifacts to Central due to indemnity clause in ToS :
https://central.sonatype.org/publish/producer-terms/
My priority is to firewall our Nexus instance and host our repo via Apache at :
https://build.shibboleth.net/maven
As to whether someone else publishes to Central (for us), I think they would need to indemnify us but we do not really exist (as a legal entity).
Looking for confirmation - technical details in the agenda above.
Making some progress running Nexus/Jenkins in ECS/Fargate using Docker Compose (which wraps CloudFormation) - is that ok ?
Plan is to use docker-compose.yml as infrastructure-as-code, open to alternatives (awscli, AWS console, Terraform) but this seems simplest / easiest.
Working through IdP browser tests in Jenkins with Jetty 9.4 versions (a) up to 9.4.43 as well as (b) 9.4.44 and up (conditional build step to inject idp-jetty-base version)