diff options
| author | Decebal Suiu <decebal.suiu@gmail.com> | 2013-10-03 16:13:12 +0300 |
|---|---|---|
| committer | Decebal Suiu <decebal.suiu@gmail.com> | 2013-10-03 16:13:12 +0300 |
| commit | 94085d391974d586633cb8821bdaa0f6972c4a16 (patch) | |
| tree | dec7c70c9a02eb355b38f8f8831930cfda49f776 /README.md | |
| parent | 6df8db4c34abb0fbbeddda7cee39124a53c4cdf5 (diff) | |
| download | pf4j-94085d391974d586633cb8821bdaa0f6972c4a16.tar.gz pf4j-94085d391974d586633cb8821bdaa0f6972c4a16.zip | |
Update README.md
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 9 |
1 files changed, 6 insertions, 3 deletions
@@ -163,12 +163,15 @@ The main advantage of DEVELOPMENT runtime mode for a plugin developer is that he Lets describe how DEVELOPMENT runtime mode works. -First, you can change the runtime mode using the "pf4j.mode" system property or overriding __DefaultPluginManager.getRuntimeMode()__. +First, you can change the runtime mode using the "pf4j.mode" system property or overriding `DefaultPluginManager.getRuntimeMode()`. For example I run the pf4j demo in eclipse in DEVELOPMENT mode adding only `"-Dpf4j.mode=development"` to the pf4j demo launcher. -You can retrieve the current runtime mode using __PluginManager.getRuntimeMode()__ or in your Plugin implementation with __getWrapper().getRuntimeMode()__(see [WelcomeMessage](https://github.com/decebals/pf4j/blob/master/demo/plugins/plugin1/src/main/java/ro/fortsoft/pf4j/demo/welcome/WelcomePlugin.java)). -The DefaultPluginManager determines automatically the correct runtime mode and for DEVELOPMENT mode overrides some components(pluginsDirectory is "../plugins", PropertiesPluginDescriptorFinder as PluginDescriptorFinder, DevelopmentPluginClasspath as PluginClassPath). +You can retrieve the current runtime mode using `PluginManager.getRuntimeMode()` or in your Plugin implementation with `getWrapper().getRuntimeMode()`(see [WelcomeMessage](https://github.com/decebals/pf4j/blob/master/demo/plugins/plugin1/src/main/java/ro/fortsoft/pf4j/demo/welcome/WelcomePlugin.java)). +The DefaultPluginManager determines automatically the correct runtime mode and for DEVELOPMENT mode overrides some components(pluginsDirectory is __"../plugins"__, __PropertiesPluginDescriptorFinder__ as PluginDescriptorFinder, __DevelopmentPluginClasspath__ as PluginClassPath). Another advantage of DEVELOPMENT runtime mode is that you can execute some code lines only in this mode (for example more debug messages). +If you use maven as build manger, after each dependency modification in you plugin (maven module) you must run Maven>Update Project... + + For more details see the demo application. Enable/Disable plugins |