All, I help maintain the Apache Axis project which has about 5 subprojects and we depend on committing a directory on called core-staging that builds https://axis.apache.org/ for a release vote for the subproject Axis2 that you can see here:
https://github.com/apache/axis-site/tree/master/axis2/java/core-staging/ URL for the release vote, manually committed by copying files from the build output dir to the site repo: https://axis.apache.org/axis2/java/core-staging/ This was our URL previously for svn in the Axis2 pom.xml: <distributionManagement> <site> <id>site</id> <url>scm:svn:https://svn.apache.org/repos/asf/axis/site/ax is2/java/core-staging</url> </site> </distributionManagement> This is what it is for git below, but I don't know how to specify a remote relative path to core-staging via git. https://github.com/apache/axis-axis2-java-core/blob/master/pom.xml <distributionManagement> <site> <id>site</id> <url>scm:git:https://gitbox.apache.org/repos/asf/axis-site .git</url> </site> </distributionManagement> That results in committing everything at the base of the repo but we need to commit to core staging. Best I can tell, although we are hosted on GitHub we still have to use gitbox as an Apache project for the scm URL in the pom.xml. After "mvn release:perform" , we follow these steps but somehow it needs to commit to the core-staging dir but as is, it will commit to the root folder of the repo. Any ideas on how to commit to the core-staging dir? Axis2 release docs, after 'mvn release:perform': 6. Change to the `target/checkout` directory and prepare the site using the following commands: mvn site-deploy mvn scm-publish:publish-scm -Dscmpublish.skipCheckin=true Now go to the `target/scmpublish-checkout` directory (relative to `target/checkout`) and check that there are no unexpected changes to the site. Then commit the changes.
