Du kannst nicht mehr als 25 Themen auswählen Themen müssen mit entweder einem Buchstaben oder einer Ziffer beginnen. Sie können Bindestriche („-“) enthalten und bis zu 35 Zeichen lang sein.
James Moger 8eaf843d60 Prepare 1.3.2 release vor 10 Jahren
src Merge pull request #115 from fzs/fu-close-finally vor 10 Jahren
.checkstyle Stop Checkstyle from complaining vor 10 Jahren
.classpath Add an Apache htpasswd user service vor 10 Jahren
.gitignore Ignore .ps1 and .sh files in root directory vor 10 Jahren
.project Preliminary implementation of server-side forking (issue 137) vor 11 Jahren
LICENSE Selected Apache License. Dropped : from name. Its simpler. vor 13 Jahren
NOTICE Add an Apache htpasswd user service vor 10 Jahren
README.markdown Documentation vor 11 Jahren
build.moxie Prepare 1.3.2 release vor 10 Jahren
build.xml Update to Moxie 0.8.1 and include gbapi in Maven repository on RELEASE build vor 10 Jahren
gitblit.iml Add an Apache htpasswd user service vor 10 Jahren
release.template Added maintaining a Maven repository to the build release process vor 10 Jahren
releases.moxie Prepare 1.3.2 release vor 10 Jahren

README.markdown

Gitblit

Gitblit is an open source, pure Java Git solution for managing, viewing, and serving Git repositories.
More information about Gitblit can be found here.

License

Gitblit is distributed under the terms of the Apache Software Foundation license, version 2.0.
The text of the license is included in the file LICENSE in the root of the project.

Java Runtime Requirement

Gitblit requires at Java 6 Runtime Environment (JRE) or a Java 6 Development Kit (JDK).

Getting help

Read the online documentation available at the Gitblit website
Issues, binaries, & sources @ Google Code

Building Gitblit

Eclipse is recommended for development as the project settings are preconfigured.

  1. Import the gitblit project into your Eclipse workspace.
    There will be lots of build errors.
  2. Using Ant, execute the build.xml script in the project root.
    This will download all necessary build dependencies and will also generate the Keys class for accessing settings.
  3. Select your gitblit project root and Refresh the project, this should correct all build problems.
  4. Using JUnit, execute the com.gitblit.tests.GitBlitSuite test suite.
    This will clone some repositories from the web and run through the unit tests.
  5. Execute the com.gitblit.GitBlitServer class to start Gitblit GO.

Building Tips & Tricks

  1. If you are running Ant from an ANSI-capable console, consider setting the MX_COLOR ennvironment variable before executing Ant.
    set MX_COLOR=true
  2. The build script will honor your Maven proxy settings. If you need to fine-tune this, please review the settings.moxie documentation.