aboutsummaryrefslogtreecommitdiffstats
path: root/README.md
diff options
context:
space:
mode:
authorDecebal Suiu <decebal.suiu@gmail.com>2013-02-15 11:52:00 +0200
committerDecebal Suiu <decebal.suiu@gmail.com>2013-02-15 11:52:00 +0200
commit0f77c00bcb8a38bde2f94f84bd1583c8a1efd34d (patch)
tree71dd72a8779a69af734faa42b36e9476d3d430fa /README.md
parent2acfe8039f811e46ab14fcadf6c22b1428f59949 (diff)
downloadpf4j-0f77c00bcb8a38bde2f94f84bd1583c8a1efd34d.tar.gz
pf4j-0f77c00bcb8a38bde2f94f84bd1583c8a1efd34d.zip
Update README.md
Diffstat (limited to 'README.md')
-rw-r--r--README.md4
1 files changed, 3 insertions, 1 deletions
diff --git a/README.md b/README.md
index 1914775..97534fb 100644
--- a/README.md
+++ b/README.md
@@ -34,6 +34,8 @@ In your pom.xml you must define the dependencies to PF4J artifacts with:
where ${pf4j.version} is the last pf4j version.
+You may want to check for the latest released version using [Maven Search](http://search.maven.org/#search%7Cga%7C1%7Cpf4j)
+
How to use
-------------------
@@ -51,7 +53,7 @@ It's very simple to add pf4j in your application:
In above code, I created a **DefaultPluginManager** (it's the default implementation for
**PluginManager** interface) that loads and starts all active(resolved) plugins.
-The available plugins are loaded using a **PluginClassLoader**.
+Each available plugin is loaded using a **PluginClassLoader**.
The **PluginClassLoader** contains only classes found in _classes_ and _lib_ folders of plugin and runtime classes and libraries of the required plugins.
The plugins are stored in a folder. You can specify the plugins folder in the constructor of DefaultPluginManager. If the plugins folder is not specified
than the location is returned by `System.getProperty("pf4j.pluginsDir", "plugins")`.