You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

README.markdown 2.0KB

12 years ago
12 years ago
11 years ago
12345678910111213141516171819202122232425262728293031323334353637383940
  1. Gitblit
  2. =================
  3. Gitblit is an open source, pure Java Git solution for managing, viewing, and serving [Git](http://git-scm.com) repositories.<br/>
  4. More information about Gitblit can be found [here](http://gitblit.com).
  5. License
  6. -------
  7. Gitblit is distributed under the terms of the [Apache Software Foundation license, version 2.0](http://www.apache.org/licenses/LICENSE-2.0).<br/>
  8. The text of the license is included in the file LICENSE in the root of the project.
  9. Java Runtime Requirement
  10. ------------------------------------
  11. Gitblit requires at Java 6 Runtime Environment (JRE) or a Java 6 Development Kit (JDK).
  12. Getting help
  13. ------------
  14. Read the online documentation available at the [Gitblit website](http://gitblit.com)<br/>
  15. Issues, binaries, & sources @ [Google Code](http://code.google.com/p/gitblit)
  16. Building Gitblit
  17. ----------------
  18. [Eclipse](http://eclipse.org) is recommended for development as the project settings are preconfigured.
  19. 1. Import the gitblit project into your Eclipse workspace.<br/>
  20. *There will be lots of build errors.*
  21. 2. Using Ant, execute the `build.xml` script in the project root.<br/>
  22. *This will download all necessary build dependencies and will also generate the Keys class for accessing settings.*
  23. 3. Select your gitblit project root and **Refresh** the project, this should correct all build problems.
  24. 4. Using JUnit, execute the `com.gitblit.tests.GitBlitSuite` test suite.<br/>
  25. *This will clone some repositories from the web and run through the unit tests.*
  26. 5. Execute the *com.gitblit.GitBlitServer* class to start Gitblit GO.
  27. Building Tips & Tricks
  28. ----------------------
  29. 1. If you are running Ant from an ANSI-capable console, consider setting the `MX_COLOR` ennvironment variable before executing Ant.<pre>set MX_COLOR=true</pre>
  30. 2. The build script will honor your Maven proxy settings. If you need to fine-tune this, please review the [settings.moxie](http://gitblit.github.io/moxie/settings.html) documentation.