OK, I think I've gotten deployment of our Maven artifacts to a
"staging repository" to work. I committed a change to the uimaj
pom.xml:
<distributionManagement>
<repository>
<id>staging-repository</id>
<url>
scpexe://people.apache.org/home/alally/public_html/uima-2.2.0-incubating/maven/
</url>
</repository>
</distributionManagement>
This URL indicates the location of the repository. We can continue to
use my public_html directory, or Thilo could change this to his to be
consistent with the locations of the distribution files, it doesn't
matter to me. I already did one deployment, you can see what it looks
like here:
http://people.apache.org/~alally/uima-2.2.0-incubating/maven
The maven command to run (from the uimaj directory) to do the deployment is:
mvn source:jar deploy
Note that, for Windows, in order to do a deployment you also have to
update your Maven settings.xml file to indicate your ssh client. For
me, this file is in Document And Settings/Administrator/.m2. I added
the following stanza:
<servers>
<server>
<id>staging-repository</id>
<username>alally</username>
<privateKey>c:/alally/keys/alally.ppk</privateKey>
<configuration>
<sshExecutable>plink</sshExecutable>
<scpExecutable>pscp</scpExecutable>
</configuration>
</server>
</servers>
which works if you have putty installed (be sure to point at your own
privateKey file though). I got the instructions from here:
http://maven.apache.org/plugins/maven-deploy-plugin/examples/deploy-ssh-external.html
I will try to add a -deploy option to extractAndBuild script which
will execute this, and I plan to (eventually) put this information on
the Wiki "Instructions for Committers" page.
-Adam
