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.
James Moger ff3f0e3533 Documentation 12 yıl önce
distrib Eliminated Lucene settings 12 yıl önce
docs Documentation 12 yıl önce
groovy Return command-specific rejection result if authz check fails. 12 yıl önce
resources Documentation 12 yıl önce
src Documentation 12 yıl önce
tests/com/gitblit/tests Implemented Lucene search result paging 12 yıl önce
tools Implemented a Federation Client. Bare clone tweaks. Documentation. 12 yıl önce
.checkstyle Findbugs. CodePro Audit. Checkstyle. Unit test refactoring. 13 yıl önce
.classpath Added Lucene Memory lib dependency 12 yıl önce
.gitignore Update to Bootstrap 2.0 12 yıl önce
.project Findbugs. CodePro Audit. Checkstyle. Unit test refactoring. 13 yıl önce
LICENSE Selected Apache License. Dropped : from name. Its simpler. 13 yıl önce
NOTICE Documentation 12 yıl önce
README.markdown Documentation. 13 yıl önce
build.xml Update to Bootstrap 2.0 12 yıl önce
checkstyle.xml Findbugs. CodePro Audit. Checkstyle. Unit test refactoring. 13 yıl önce
test-gitblit.properties Revised unit tests. Swapped BlueZGnome repo (unacessible) for Gitective. 12 yıl önce
test-users.conf Unit testing overhaul. 12 yıl önce

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.Launcher class to start Gitblit.