首先得安装 Subversion 库函数

				    wget http://mirrors.hust.edu.cn/apache/subversion/subversion-1.8.8.tar.gz

    tar xzf subversion-1.8.8.tar.bz2 

    cd subversion-1.8.8

    subversion-1.8.8 aliang$ ./autogen.sh 
        buildcheck: checking installation...
        buildcheck: autoconf not found.
                    You need autoconf version 2.59 or newer installed.

    brew install autoconf
        ==> Downloading https://downloads.sf.net/project/machomebrew/Bottles/autoconf-2.69.mavericks.bottle.tar.gz
        #################################################### 100.0%
        ==> Pouring autoconf-2.69.mavericks.bottle.tar.gz
        🍺 /usr/local/Cellar/autoconf/2.69: 69 files, 2.0M

    ./autogen.sh 
        buildcheck: checking installation...
        buildcheck: autoconf version 2.69 (ok)
        buildcheck: autoheader version 2.69 (ok)
        buildcheck: libtool not found.
        You need libtool version 1.4 or newer installed

    brew install libtool
        Warning: A newer Command Line Tools release is available
        Update them from Software Update in the App Store.
        ==> Downloading https://downloads.sf.net/project/machomebrew/Bottles/libtool-2.4.2.mavericks.bottle.2.tar.gz
        ##################################################### 100.0%
        ==> Pouring libtool-2.4.2.mavericks.bottle.2.tar.gz
        ==> Caveats
        In order to prevent conflicts with Apple''s own libtool we have prepended a "g"
        so, you have instead: glibtool and glibtoolize.
        ==> Summary
        🍺  /usr/local/Cellar/libtool/2.4.2: 66 files, 2.2M

    ./autogen.sh 
        buildcheck: checking installation...
        buildcheck: autoconf version 2.69 (ok)
        buildcheck: autoheader version 2.69 (ok)
        buildcheck: libtool version 2.4.2 (ok)
        Copying libtool helper: /usr/local/share/aclocal/libtool.m4
        Copying libtool helper: /usr/local/share/aclocal/ltoptions.m4
        Copying libtool helper: /usr/local/share/aclocal/ltsugar.m4
        Copying libtool helper: /usr/local/share/aclocal/ltversion.m4
        Copying libtool helper: /usr/local/share/aclocal/lt~obsolete.m4
        Creating build-outputs.mk...
        Creating svn_private_config.h.in...
        Creating configure...

        You can run ./configure now.

        Running autogen.sh implies you are a maintainer.  You may prefer
        to run configure in one of the following ways:

        ./configure --enable-maintainer-mode
        ./configure --disable-shared
        ./configure --enable-maintainer-mode --disable-shared
        ./configure --disable-optimize --enable-debug
        ./configure CUSERFLAGS='--flags-for-C' CXXUSERFLAGS='--flags-for-C++'

        Note:  If you wish to run a Subversion HTTP server, you will need
        Apache 2.x.  See the INSTALL file for details.

    brew install swig
        ==> Downloading http://downloads.sourceforge.net/project/swig/swig/swig-2.0.11/swig-2.0.11.tar.gz
        ######################################################################## 100.0%
        ==> ./configure --prefix=/usr/local/Cellar/swig/2.0.11
        ==> make
        ==> make install
        🍺  /usr/local/Cellar/swig/2.0.11: 597 files, 6.2M, built in 10.1 minutes 

    ./configure --with-swig=/usr/local/bin/swig
        configure: Configuring Subversion 1.8.8
        ... ...
        ==================================================================
        WARNING: You have chosen to compile Subversion with a different
                 compiler than the one used to compile Apache.

            Current compiler:  gcc
           Apache's compiler:  /Applications/Xcode.app/Contents/Developer/Toolchains/OSX10.9.xctoolchain/usr/bin/cc

        This could cause some problems.
        ==================================================================
        ... ...

    make swig-py
    make install
    make check-swig-py        
    sudo make install-swig-py

    sudo cp -r /usr/local/lib/svn-python/ /Library/Python/2.7/site-packages/

		

执行转换命令

				    mkdir hgpath

    cd hgpath

    hg init

    hg convert -s svn -d hg ${local_path} ./hgpath

		

注意，这里转换的 SVN 目录只能是仓库目录而不是工作目录

解压至 D:\JavaSoft\git-1.7.7.1

增加系统环境路径：D:\JavaSoft\git-1.7.7.1\bin;D:\JavaSoft\git-1.7.7.1\cmd;

设置系统属性：
git config --global user.name "your.name"
git config --global user.email git.mail.name@gmail.com

创建密钥：

mkdir /.ssh

ssh-keygen -f D:\JavaSoft\git-1.7.7.1\.ssh\id_rsa -t rsa -C 'git.mail.name@gmail.com' -t rsa

复制 id_rsa.pub 的内容，到github.com增加公钥，然后粘贴保存。

测试：git -v -T git@github.com

Hi your.name! You've successfully authenticated, but GitHub does not provide shell access.

Some of you may be familiar with the (not very user friendly) exception message
javax.net.ssl.SSLHandshakeException:
sun.security.validator.ValidatorException:
PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException:
unable to find valid certification path to requested target

when trying to open an SSL connection to a host using JSSE. What this usually means is that the server is using a test certificate (possibly generated using keytool) rather than a certificate from a well known commercial Certification Authority such as Verisign or GoDaddy. Web browsers display warning dialogs in this case, but since JSSE cannot assume an interactive user is present it just throws an exception by default.

Certificate validation is a very important part of SSL security, but I am not writing this entry to explain the details. If you are interested, you can start by reading the Wikipedia blurb. I am writing this entry to show a simple way to talk to that host with the test certificate, if you really want to.

Basically, you want to add the server's certificate to the KeyStore with your trusted certificates. There are any number of ways to achieve that, but a simple solution is to compile and run the attached program as java InstallCert hostname, for example

% java InstallCert ecc.fedora.redhat.com
Loading KeyStore /usr/jdk/instances/jdk1 .5.0 /jre/lib/security/cacerts
Opening connection to ecc.fedora.redhat.com: 443
Starting SSL handshake

javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
    at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java: 150 )
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java: 1476 )
    at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java: 174 )
    at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java: 168 )
    at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java: 846 )
    at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java: 106 )
    at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java: 495 )
    at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java: 433 )
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java: 815 )
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java: 1025 )
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java: 1038 )
    at InstallCert.main(InstallCert.java: 63 )
Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException:
unable to find valid certification path to requested target
    at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java: 221 )
    at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java: 145 )
    at sun.security.validator.Validator.validate(Validator.java: 203 )
    at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java: 172 )
    at InstallCert$SavingTrustManager.checkServerTrusted(InstallCert.java: 158 )
    at com.sun.net.ssl.internal.ssl.JsseX509TrustManager.checkServerTrusted(SSLContextImpl.java: 320 )
    at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java: 839 )
      7  more
Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
    at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java: 236 )
    at java.security.cert.CertPathBuilder.build(CertPathBuilder.java: 194 )
    at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java: 216 )
      13  more

Server sent  2  certificate(s):

  1  Subject CN = ecc.fedora.redhat.com ,  O = example.com ,  C = US
   Issuer  CN = Certificate Shack ,  O = example.com ,  C = US
   sha1    2e 7f  76  9b  52   91   09  2e 5d 8f 6b  61   39  2d 5e  06  e4 d8 e9 c7 
   md5     dd d1 a8  03  d7 6c 4b  11  a7 3d  74   28   89  d0  67   54  

  2  Subject CN = Certificate Shack ,  O = example.com ,  C = US
   Issuer  CN = Certificate Shack ,  O = example.com ,  C = US
   sha1    fb  58  a7  03  c4 4e 3b 0e e3 2c  40  2f  87   64   13  4d df e1 a1 a6 
   md5      72  a0  95   43  7e  41   88   18  ae 2f 6d  98   01  2c  89   68  

Enter certificate to add to trusted keystore or 'q' to quit:  [ 1 ]

What happened was that the program opened a connection to the specified host and started an SSL handshake. It printed the exception stack trace of the error that occured and shows you the certificates used by the server. Now it prompts you for the certificate you want to add to your trusted KeyStore. You should only do this if you are sure that this is the certificate of the trusted host you want to connect to. You may want to check the MD5 and SHA1 certificate fingerprints against a fingerprint generated on the server (e.g. using keytool) to make sure it is the correct certificate.

If you've changed your mind, enter 'q'. If you really want to add the certificate, enter '1'. (You could also add a CA certificate by entering a different certificate, but you usually don't want to do that'). Once you have made your choice, the program will print the following:

It displayed the complete certificate and then added it to a Java KeyStore 'jssecacerts' in the current directory. To use it in your program, either configure JSSE to use it as its trust store (as explained in the documentation) or copy it into your $JAVA_HOME/jre/lib/security directory. If you want all Java applications to recognize the certificate as trusted and not just JSSE, you could also overwrite the cacerts file in that directory.

After all that, JSSE will be able to complete a handshake with the host, which you can verify by running the program again:

% java InstallCert ecc.fedora.redhat.com Loading KeyStore jssecacerts
 Opening connection to ecc.fedora.redhat.com:443
 Starting SSL handshake
 No errors, certificate is already trusted Server sent 2 certificate(s): 1 []

Enter certificate to add to trusted keystore or 'q' to quit: [1] q KeyStore not changed 

设置服务器端的 JVM:JAVA_OPTS="-server -Xms3000m -Xmx3000m -Xss512k"

-server:一定要作为第一个参数，在多个CPU时性能佳

-Xms：初始Heap大小，使用的最小内存

-Xmx：java heap最大值，使用的最大内存

上面两个值一般设置为同样的大小。

-Xss：每个线程的Stack大小

-verbose:gc 现实垃圾收集信息

-Xloggc:gc.log 指定垃圾收集日志文件

刚刚了解到的一些参数（待实践测试）

-Xmn：young generation的heap大小，一般设置为Xmx的3、4分之一

-XX:+UseParNewGC ：缩短minor收集的时间

-XX:+UseConcMarkSweepGC ：缩短major收集的时间

提示：此选项在Heap Size 比较大而且Major收集时间较长的情况下使用更合适

1. 首先将Subversion安装目录bin\下面的两个文件：mod_authz_svn.so和mod_dav_svn.so复制到Apache安装目录modules\目录下。
   
2. 找到Apache安装目录下的conf目录，用文本编辑器打开httpd.conf，找到一下两行：
   
   #LoadModule dav_module modules/mod_dav.so
   #LoadModule dav_fs_module modules/mod_dav_fs.so
   
   将每行前面的注释符"#"去掉。再在所有LoadModule语句的最后添加一下几行：
   
   #SVN
LoadModule dav_svn_module modules/mod_dav_svn.so
LoadModule authz_svn_module modules/mod_authz_svn.so
<Location /svn>
DAV svn
SVNParentPath "E:/svnrepos"
</Location>
   

但是使用启动测试一直有错，返回

Syntax error on line 143 of C:\apache\conf\httpd.conf: API module structure 'dav_svn_module' in file C:\apache\modules\mod_dav_svn.so is garbled - perhaps this is not an Apache module DSO?
Apache could not be started

后来再看资料，好像是SVN1.4.3提供的so文件只支持APACHE2.0，并不支持2.2版本的，除非重新编译。好在已经有人解决了，下载了一个支持APACHE2.2的，但却是SVN1.3.2的，死马当活马医了，放到SVN1.4中居然也可以，hoho~~。我是把所有和SVN有关的文件（含动态连接库文件）全部放在了APACHE安装目录的svn目录里，配置文件如下：

LoadModule dav_svn_module svn/mod_dav_svn_1.3.so
LoadModule authz_svn_module svn/mod_authz_svn_1.3.so
<Location /svn>
DAV svn
SVNParentPath "E:/svnrepos"
</Location>

Technorati : SVN APACHE

API地址： http://www.blogjava.net/ideame/services/metaweblog.aspx


isOK。wonderful !