[MSITE-1015] Get rid of Wagon dependency

[jira-importer]

Konrad Windszus opened MSITE-1015 and commented

As Maven Wagon is lacking maintenance and most of the sites leverage https://maven.apache.org/plugins/maven-scm-publish-plugin/ nowadays to deploy a site we should get rid of the Wagon dependency and support certain transport protocols directly:

1. GitHub Pages via https://docs.github.com/en/rest/pages/pages?apiVersion=2022-11-28#create-a-github-pages-deployment, the ReST API for uploading the artifact is not documented
2. SCMs via https://maven.apache.org/scm/
3. SFTP via https://github.com/apache/mina-sshd/blob/master/docs/sftp.md

This would allow to get rid of one abstraction layer, improve error reporting and finally deprecate https://maven.apache.org/plugins/maven-scm-publish-plugin/.

---

No further details from MSITE-1015

[jira-importer]

Michael Osipov commented

the description you provide only applies to the projects at ASF, you cannot use it for other projects, especially private ones. Please still need through SCM, SFTP, WebDAV and file.

[jira-importer]

Konrad Windszus commented

1. File deployment doesn't need Wagon (nor even site-deploy).
2. SCM is part of this proposal
3. SFTP is as well
4. WebDAV is not but IMHO almost nowhere used any longer

[jira-importer]

Michael Osipov commented

You cannot make this assumption about 4. You do not know, nor do I know. I will not make such an assumption.
At the moment, nothing is broken with Wagon, it just works.

[kwin]

In order to reduce dependency clutter it would probably be good to separate these out into dedicated file deployment/publish plugins. Those can then be used to deploy arbitrary file system structures (not only sites). The only thing which is specific to site deployment is really https://maven.apache.org/pom.html#Site_Distribution...
This relates a bit to apache/maven-site#1440.