diff options
| -rw-r--r-- | README.md | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -201,7 +201,7 @@ Also, you can control plugin instance creation overriding `createPluginFactory` For more information please see the demo sources. -** Note** If your application didn't find extensions then make sure that you have a file with name `extensions.idx` +**NOTE:** If your application didn't find extensions then make sure that you have a file with name `extensions.idx` generated by PF4J in the plugin jar. It's most likely that they are some problems with the annotation processing mechanism from Java. O possible solution to resolve your problem is to add a configuration to your maven build. @@ -276,7 +276,7 @@ You can retrieve the current runtime mode using `PluginManager.getRuntimeMode()` 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). -**Note:** If you use Eclipse than make sure annotation processing is enabled at least for any projects registering objects using annotations. In the properties for your new project go to __Java Compiler > Annotation Processing__ +**NOTE:** If you use Eclipse than make sure annotation processing is enabled at least for any projects registering objects using annotations. In the properties for your new project go to __Java Compiler > Annotation Processing__ Check the __“Enable Project Specific Settings”__ and make sure __“Enable annotation processing”__ is checked. If you use Maven as build manger, after each dependency modification in your plugin (Maven module) you must run __Maven > Update Project...__ |