Ported this forward to the main branches. It lands a little differently because of the refactoring work that was done, and because the MDA wasn’t included in the earlier work, but it’s basically the same stuff and most of it looks like cherry-picks.

As with the IdP on the maintenance branch, this includes a dependency banning stanza (in the IdP and MDA) that should prevent accidental inclusion of artifacts with the old name.

Note to self: the other thing I didn’t update from Rod’s original list of places he thought would be affected is the MDA, but that’s because that’s on the Java 17 stack now. I’ll take care of that when I port all of this over to that branch.

I don’t know precisely what dependencies it needs I guess, my thought was they might be sufficiently minimal to make it less of a problem.

Is it possible that we should just create a separate parent for this?

Or leave it unparented. My concern is that it then adds another place where we need to duplicate all the work to move our dependencies forward (amongst all the other reasons why we have a parent),

I’m easily persuaded either way