diff options
| author | Decebal Suiu <decebal.suiu@gmail.com> | 2013-10-03 16:15:46 +0300 |
|---|---|---|
| committer | Decebal Suiu <decebal.suiu@gmail.com> | 2013-10-03 16:15:46 +0300 |
| commit | cd327605d0fa4a251a867413ffcd376e3823e872 (patch) | |
| tree | 742680ce2ddb1fb2a84060703814172de5f3a4d6 /README.md | |
| parent | 94085d391974d586633cb8821bdaa0f6972c4a16 (diff) | |
| download | pf4j-cd327605d0fa4a251a867413ffcd376e3823e872.tar.gz pf4j-cd327605d0fa4a251a867413ffcd376e3823e872.zip | |
Update README.md
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -165,7 +165,7 @@ Lets describe how DEVELOPMENT runtime mode works. 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)). +You can retrieve the current runtime mode using `PluginManager.getRuntimeMode()` or in your Plugin implementation with `getWrapper().getRuntimeMode()`(see [WelcomePlugin](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). |