move developer info to wiki

Author: Vladimir Kotal

README.md

@@ -526,259 +526,7 @@ See https://github.com/oracle/opengrok/wiki/Webapp-configuration
 
 ## 8. Information for developers
 
-### 8.0 Building
-
-Just run `ant` from command line in the top-level directory or use build
-process driven by graphical developer environment such as Netbeans.
-
-Note: in case you are behind http proxy, use `ANT_OPTS` to download jflex, lucene.
-E.g.
-```bash
-ANT_OPTS="-Dhttp.proxyHost=?.? -Dhttp.proxyPort=80" ant
-```
-
-#### 8.0.1 Package build
-
-Run `ant package` to create package (specific for the operating system this is
-being executed on) under the `dist/` directory.
-
-### 8.1 Unit testing
-
-**Note**: For full coverage report, a proper junit test environment is required.
-That would mean:
-
-  * You have to use Ant 1.9 and above
-  * At least `junit-4.12.jar` and its dependencies have to be in ant's
-    classpath (e.g. in `./lib`). The test task will download them automatically.
-  * Your `PATH` must contain directory with exuberant ctags binary
-    * **Note**: make sure that the directory which contains exuberant ctags binary
-      is prepended before the directory with plain ctags program.
-  * Your `PATH` variable must contain directories which contain binaries of
-    appropriate SCM software which means commands hg, sccs, cvs, git, bzr, svn
-    (svnadmin too). They must be available for the full report.
-
-The tests are then run as follows:
-
-```bash
-ant -lib ./lib test
-```
-
-To check if the test completed without error look for `AssertionFailedError`
-occurrences in the `TESTS-TestSuites.xml` file produced by the test run.
-
-### 8.2 Using Findbugs
-
-If you want to run Findbugs (<http://findbugs.sourceforge.net/>) on OpenGrok,
-you have to download Findbugs to your machine, and install it where you have
-checked out your OpenGrok source code, under the `lib/findbugs` directory,
-like this:
-
-```bash
-cd ~/.ant/lib
-wget http://..../findbugs-x.y.z.tar.gz
-gtar -xf findbugs-x.y.z.tar.gz
-mv findbugs-x.y.z findbugs
-```
-
-You can now run ant with the findbugs target:
-
-```
-$ ant findbugs
-...
-findbugs:
- [findbugs] Executing findbugs from ant task
- [findbugs] Running FindBugs...
- [findbugs] Warnings generated: nnn
- [findbugs] Output saved to findbugs/findbugs.html
-```
-
-Now, open `findbugs/findbugs.html` in a web-browser, and start fixing bugs!
-
-If you want to install findbugs some other place than `~/.ant/lib`, you can
-untar the `.tar.gz` file to a directory, and use the `findbugs.home` property to
-tell ant where to find findbugs, like this (if you have installed fundbugs
-under the lib directory):
-
-```bash
-ant findbugs -Dfindbugs.home=lib/findbug
-```
-
-There is also a `findbugs-xml` ant target that can be used to generate XML files
-that can later be parsed, e.g. by Jenkins.
-
-### 8.3 Using Jacoco
-
-If you want to check test coverage on OpenGrok, download jacoco from
-<http://www.eclemma.org/jacoco/>. Place `jacocoagent.jar` and `jacocoant.jar` in the
-`opengrok/lib`, `~/.ant/lib` or into classpath (`-lib` option of ant).
-
-Now you can instrument your classes and test them run:
-
-```bash
-ant -Djacoco=true -Djacoco.home=/<path_to>/jacoco jacoco-code-coverage
-```
-
-Now you should get output data in `jacoco.exec`
-
-Look at `jacoco/index.html` to see how complete your tests are.
-
-### 8.4 Using Checkstyle
-
-To check that your code follows the standard coding conventions,
-you can use checkstyle from <http://checkstyle.sourceforge.net/>
-
-First you must download checkstyle from <http://checkstyle.sourceforge.net/>.
-You need Version 6.8 (or newer). Extract the package you have
-downloaded, and create a symbolic link to it from `~/.ant/lib/checkstyle`,
-e.g. like this:
-
-```bash
-cd ~/.ant/lib
-unzip ~/Desktop/checkstyle-7.6.zip
-ln -s checkstyle-7.6 checkstyle
-```
-
-You also have to create symbolic links to the jar files:
-
-```bash
-cd checkstyle
-ln -s checkstyle-7.6-all.jar checkstyle-all.jar
-```
-
-To run checkstyle on the source code, just run ant checkstyle:
-
-```bash
-ant checkstyle
-```
-
-Output from the command will be stored in the checkstyle directory.
-
-If you want to install checkstyle some other place than `~/.ant/lib`, you can
-untar the `.tar.gz` file to a directory, and use the `checkstyle.home` property
-to tell ant where to find checkstyle, like this (if you have installed
-checkstyle under the lib directory):
-
-```bash
-ant checkstyle -Dcheckstyle.home=lib/checkstyle
-```
-
-### 8.5 Using PMD and CPD
-
-To check the quality of the OpenGrok code you can also use PMD
-from <https://pmd.github.io/>.
-
-How to install:
-
-```bash
-cd ~/.ant/lib
-unzip ~/Desktop/pmd-bin-5.5.4.zip
-ln -s pmd-5.5.4/ pmd
-```
-
-To run PMD on the source code, just run ant pmd:
-
-```bash
-ant -Dpmd.home=~/.ant/lib/pmd pmd
-```
-
-Output from the command will be stored in the pmd subdirectory:
-
-```
-$ ls pmd
-pmd_report.html  pmd_report.xml
-```
-
-If you want to install PMD some other place than `~/.ant/lib`, you can
-unzip the `.zip` file to a directory, and use the `pmd.home` property
-to tell ant where to find PMD, like this (if you have installed
-PMD under the `./ext_lib directory`):
-
-```bash
-ant pmd -Dpmd.home=ext_lib/pmd
-```
-
-To run CPD, just use the same as above, but use targets:
-
-```bash
-ant -Dpmd.home=ext_lib/pmd cpd cpd-xml
-```
-
-Which will result in:
-
-```
-$ ls pmd
-cpd_report.xml cpd_report.txt
-```
-
-### 8.6 Using JDepend
-
-To see dependencies in the source code, you can use JDepend from
-<https://github.com/clarkware/jdepend>.
-
-How to install:
-
-```bash
-cd ~/.ant/lib
-unzip ~/Desktop/jdepend-2.9.1.zip
-ln -s jdepend-2.9.1/ jdepend
-cd jdepend/lib
-ln -s jdepend-2.9.1.jar jdepend.jar
-```
-
-How to analyze:
-
-```bash
-ant jdepend
-```
-
-Output is stored in the jdepend directory:
-
-```
-$ ls jdepend/
-report.txt  report.xml
-```
-
-### 8.7 Using SonarQube
-
-Use a sonar runner with included `sonar-project.properties` properties,
-e.g. using bash:
-
-```bash
-cd <checkout_dir> # it has to contain sonar-project.properties!
-export SONAR_RUNNER_OPTS="-Xmx768m -XX:MaxPermSize=256m"
-export SERVERIP=10.163.26.78
-~//Projects/sonar-runner-2.3/bin/sonar-runner \
-    -Dsonar.host.url=http://${SERVERIP}:9000 \
-    -Dsonar.jdbc.url=jdbc:h2:tcp://${SERVERIP}:9092/sonar
-```
-
-### 8.8 Using Travis CI
-
-Travis depends on updated and working maven build.
-Please see `.travis.yml`, if your branch has this file,
-you should be able to connect your Github to Travis CI.
-OpenGroks Travis is here: <https://travis-ci.org/OpenGrok/OpenGrok>
-
-### 8.9 Maven
-
-The build can now be done through Maven (<https://maven.apache.org/>) which takes care of the dependency management
-and setup (calls Ant for certain actions).
-
-#### 8.9.1 Unit Testing
-
-You can test the code at the moment by running `./mvnw test` which will execute *all* tests.
-Conditionally, if you don't have every type of repository installed, you can set it to unit-test only those which are
-found to be working on your system.
-
-```bash
-./mvnw test -Djunit-force-all=false
-```
-
-You can also force a specific repository test from running through the following system property
-
-```bash
-./mvnw test -Djunit-force-all=false -Djunit-force-git=true
-```
+See https://github.com/oracle/opengrok/wiki/Developer-intro and https://github.com/oracle/opengrok/wiki/Developers
 
 ## 9. Tuning OpenGrok for large code bases