This is an automated email from the git hooks/post-receive script. pini pushed a commit to tag upstream/1.1.0_beta1 in repository sikuli.
commit 5851ad81559f59bcd9f58e4752b5aeb5f038e2e8 Author: Raimund Hocke <[email protected]> Date: Mon Jan 6 14:25:59 2014 +0100 Update README.md --- README.md | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 65d13b2..06ef93d 100644 --- a/README.md +++ b/README.md @@ -172,8 +172,14 @@ As it is standard with Maven, all -D parameters go to Java system properties, wh [please look here](https://github.com/RaiMan/SikuliX-2014/wiki/How-to-produce-the-ready_to_use-jar-packages) -**--- How to deploy to a Maven repository ---** +**--- How to deploy to a private Maven repository ---** -Edit/configure the repository - see `distributionManagement` in `pom.xml`. -Then run `mvn deploy -PwithDocs,withSource`. Maybe `-DaltDeploymentRepository=...` will also -be needed - see `pom.xml`. +Edit/configure the repository in section `distributionManagement` in root `pom.xml`.<br /> +The current setting is to the local copy of the peer Git Repo SikuliX-Maven-Repo here (after deployment you have to run a commit and trigger a push, to get it on GitHub).<br /> +This approch [comes from here ...](http://cemerick.com/2010/08/24/hosting-maven-repos-on-github/). + + +To make a deploy run <br /> +`mvn deploy -PwithDocs,withSource` + +With Maven < 3.0 you might need `-DaltDeploymentRepository=...` additionally. -- Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-java/sikuli.git _______________________________________________ pkg-java-commits mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-commits
