Push the site with git instead of maven-scm-publish-plugin

[slachiewicz]

The first real run failed, on codehaus-plexus.github.io:

[INFO] Checking out the pub tree from scm:git:git@github.com:codehaus-plexus/codehaus-plexus.github.io.git
[INFO] Executing: git clone --branch master 'slachiewicz:********@github.com:codehaus-plexus/...'
[ERROR] ssh: Could not resolve hostname slachiewicz: Temporary failure in name resolution

Why my approach could never have worked

The workflow passed -Dscmpublish.pubScmUrl=…https… to force an https URL. The plugin ignored it and used the ssh URL from scm.developerConnection.

That is Maven plugin parameter precedence: the parent POM sets

<pubScmUrl>${project.scm.developerConnection}</pubScmUrl>

explicitly in <configuration>, and an explicitly configured value always beats the ${scmpublish.pubScmUrl} user property. So the -D was silently discarded — no warning, no error, just the wrong URL. This would have failed identically in all fifteen repositories; the org page was simply the first one tried.

Good argument for the dry-run input, which is how this surfaced without anything being published.

The fix

Maven still builds the site — that part was never the problem. Only the push changes:

1. clone the target branch with the job token over https
2. rsync -a --delete the built site over it, so pages deleted upstream disappear from the published site too, which is what scm-publish did for us
3. commit and push, or, on a dry run, print what would change and stop

No plugin URL resolution involved, and every step is readable in the workflow.

publish-branch input

This also replaces #65, which I opened an hour ago to make the branch come from the POM. That was the right instinct — the org page is served from master, not gh-pages — but the wrong mechanism, since the workflow now does the push itself and cannot read scmBranch out of the POM.

So it is an explicit input, defaulting to gh-pages. codehaus-plexus.github.io passes master. #65 is superseded; I'll close it.

Unexplained, and now moot

The clone URL came out as slachiewicz:********@github.com: — maven-scm injected a username from somewhere I could not identify on a clean runner. It does not matter under the new approach, but I am flagging it rather than pretending I understood it.

Please dry-run again after merging

Callers need no change except codehaus-plexus.github.io, which needs publish-branch: master — I'll update that PR.