Hi, Currently the source for the Jackrabbit website is maintained at https://svn.apache.org/repos/asf/jackrabbit/site/trunk/. The Maven site build generates the target site out of that and the maven-scm-publish-plugin pushes the generated site to https://svn.apache.org/repos/asf/jackrabbit/site/live/jcr/ afterwards. The last step is the tool svnpubsub (executed by ASF INFRA) publishing those files to https://jackrabbit.apache.org/
I propose to create a new git repository for the Jackrabbit (2) site source at https://gitbox.apache.org/repos/asf/jackrabbit-site.git / https://github.com/apache/jackrabbit-site and let INFRA migrate the SVN repository location https://svn.apache.org/repos/asf/jackrabbit/site/trunk/ into that new repo (keeping the history) That is the last active piece of the puzzle in the Jackrabbit ecosystem which is still leveraging SVN. Note: I don’t propose to change the SVN repository containing the "generated site” at https://svn.apache.org/repos/asf/jackrabbit/site/live/. That is currently the target of multiple sources, namely - https://github.com/apache/jackrabbit-filevault/tree/master/src/site - https://github.com/apache/jackrabbit-filevault-package-maven-plugin/tree/master/src/site and - https://github.com/apache/jackrabbit-oak/tree/trunk/oak-doc/src/site I don’t think there is an urgent need for changing this to Git as well, as the active work uses the source repository locations only. WDYT? Konrad
