aboutsummaryrefslogtreecommitdiffstats
path: root/README.md
diff options
context:
space:
mode:
authorDecebal Suiu <decebal.suiu@gmail.com>2014-06-04 16:37:50 +0300
committerDecebal Suiu <decebal.suiu@gmail.com>2014-06-04 16:37:50 +0300
commit766681abb48605f2cebfb6fe571ef2ea025287f6 (patch)
tree818ca835b502981faab6ba42e850800ddf255f59 /README.md
parentf508484004b0d71bd146eadd0cb1f7de1db43952 (diff)
downloadpf4j-766681abb48605f2cebfb6fe571ef2ea025287f6.tar.gz
pf4j-766681abb48605f2cebfb6fe571ef2ea025287f6.zip
Update README.md
Diffstat (limited to 'README.md')
-rw-r--r--README.md7
1 files changed, 7 insertions, 0 deletions
diff --git a/README.md b/README.md
index 9ac353b..a216908 100644
--- a/README.md
+++ b/README.md
@@ -157,6 +157,13 @@ and in plugin respository you must have a plugin.properties file with the below
For more information please see the demo sources.
+Plugin assembly
+------------------------------
+
+After you developed a plugin the next step is to deploy it in your application. For this task, you must create a zip file with a structure described in section "How to use" from the beginning of the document.
+If you use `apache maven` as build manger than your pom.xml file must looks like [this](https://github.com/decebals/pf4j/blob/master/demo/plugins/plugin1/pom.xml). This file it's very simple and it's self explanatory.
+If you use `apache ant` than your buil.xml file must looks like [this](https://github.com/gitblit/gitblit-powertools-plugin/blob/master/build.xml). In this case please look at the "build" target.
+
Plugin lifecycle
--------------------------
Each plugin passes through a pre-defined set of states. [PluginState](https://github.com/decebals/pf4j/blob/master/pf4j/src/main/java/ro/fortsoft/pf4j/PluginState.java) defines all possible states.