From bd7db1070e07cf1777a0c0ee6e770625f8734fb6 Mon Sep 17 00:00:00 2001
From: James Moger <james.moger@gitblit.com>
Date: Tue, 15 Apr 2014 09:53:10 -0400
Subject: [PATCH] Merge pr-170 'ticket-fix' from https://github.com/lucidd/gitblit
---
src/site/plugins_overview.mkd | 7 ++++---
1 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/src/site/plugins_overview.mkd b/src/site/plugins_overview.mkd
index 29fc8aa..45a5434 100644
--- a/src/site/plugins_overview.mkd
+++ b/src/site/plugins_overview.mkd
@@ -20,9 +20,10 @@
A plugin defines it's metadata in the META-INF/MANIFEST.MF file:
Plugin-Id: powertools
- Plugin-Description: Gitblit Powertools
+ Plugin-Description: Command and control Gitblit over SSH
Plugin-Class: com.gitblit.plugin.powertools.Powertools
Plugin-Version: 1.2.0
+ Plugin-Requires: 1.5.0
Plugin-Provider: gitblit.com
In addition to extending Gitblit core, plugins can also define extension points that may be implemented by other plugins. Therefore a plugin may depend on other plugins.
@@ -32,9 +33,9 @@
**NOTE:**
The pf4j plugin framework relies on a javac apt processor to generate compile-time extension information, so be sure to enable apt processing in your build process.
-#### Limitations of Dependencies & Requires
+#### Limitations of Dependencies
-Plugins may specify dependencies by ID, but may not specify specific versions of a dependency. The plugin registry allows you to specify a *requires* version of Gitblit, but this is not currently enforced.
+Plugins may specify dependencies by ID, but may not specify specific versions of a dependency.
### Managing Plugins
--
Gitblit v1.9.1