There usually are 3 directories at the same level
The source directory is version-controlled by git, the other two are version controlled by svn. While the source directory and the distribution directory can have arbitrary names and locations, the site directory has to be called site and it needs to be at the same level as the source directory to enable site deployment.
Assuming that the source directory is available one can create the directory structure by going to the directory that contains the source directory and checking out the distribution and site directories:
$ svn co https://dist.apache.org/repos/dist/release/vxquery dist $ svn co https://svn.apache.org/repos/asf/vxquery/site
Change into the dist directory and run
$ (gpg2 --list-sigs <your name> && gpg2 --armor --export <your name>) >> KEYS
and then check the new KEYS file into svn
$ svn ci -m "add [YOUR NAME]'s key to KEYS file"
Follow the steps in the How to create a master password guide to encrypt a master password and to encrypt your Apache LDAP password. (It's nicer if you have maven > 3.2.1 to do this.)
<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd"> ... <servers> ... <!-- To publish a snapshot of some part of Maven --> <server> <id>apache.snapshots.https</id> <username>[YOUR APACHE LDAP USERNAME]</username> <password>[YOUR APACHE LDAP PASSWORD (encrypted)]</password> </server> <!-- To stage a release of some part of Maven --> <server> <id>apache.releases.https</id> <username>[YOUR APACHE LDAP USERNAME]</username> <password>[YOUR APACHE LDAP PASSWORD (encrypted)]</password> </server> ... </servers> ... </settings>
<profiles> <profile> <id>apache-release</id> <properties> <gpg.executable>gpg2</gpg.executable> <gpg.passphrase>...</gpg.passphrase> </properties> </profile> </profiles>
$ mvn clean
$ java -jar ~/<DOWLOADS FOLDER>/apache-rat-0.11/apache-rat-0.11.jar -d . -E .rat-excludes
$ mvn install -Papache-release
$ mvn release:prepare -DdryRun=true
$ mvn release:prepare $ mvn release:perform
$ mvn site site:deploy
$ cd ../site $ svn st | awk '/\?/ { print $2 }' | xargs svn add # add all new files $ svn ci -m"updated site" $ cd -