This closes #1804

docs/user-manual/en/broker-plugins.md

@@ -10,7 +10,7 @@ interface, making sure the plugin is on the classpath, and registering it with t
 
 ## Adding the plugin to the classpath
 
-The proper place to add your jar would be under $ARTEMIS_INSTANCE/lib.
+See the documentation on [adding runtime dependencies](using-server.md) to understand how to make your plugin available to the broker.
 
 If you are using an embed system than you will need the jar under the regular classpath of your embedded application.
 

docs/user-manual/en/diverts.md

@@ -28,6 +28,9 @@ of them receive the same, original message. This means that the results
 of a transformer on a message are not directly available for other
 diverts or their filters on the same address.
 
+See the documentation on [adding runtime dependencies](using-server.md) to 
+understand how to make your transformer available to the broker.
+
 A divert will only divert a message to an address on the *same server*,
 however, if you want to divert to an address on a different server, a
 common pattern would be to divert to a local store-and-forward queue,

docs/user-manual/en/intercepting-operations.md

@@ -67,8 +67,8 @@ Both incoming and outgoing interceptors are configured in
        <class-name>org.apache.activemq.artemis.jms.example.AdditionalPropertyInterceptor</class-name>
     </remoting-outgoing-interceptors>
 
-The interceptors classes (and their dependencies) must be added to the
-server classpath to be properly instantiated and called.
+See the documentation on [adding runtime dependencies](using-server.md) to 
+understand how to make your interceptor available to the broker.
 
 ## Interceptors on the Client Side
 

docs/user-manual/en/persistence.md

@@ -407,7 +407,8 @@ in the database tables is encoded using Apache ActiveMQ Artemis internal encodin
 
 To configure Apache ActiveMQ Artemis to use a database for persisting messages and bindings data you must do two things.
 
-1. Add the appropriate JDBC driver libraries to the Artemis runtime.  You can do this by dropping the relevant jars in the lib folder of the ActiveMQ Artemis distribution.
+1. See the documentation on [adding runtime dependencies](using-server.md) to 
+   understand how to make the JDBC driver available to the broker.
 
 2. Create a store element in your broker.xml config file under the ```<core>``` element.  For example:
 

docs/user-manual/en/using-server.md

@@ -460,3 +460,13 @@ Just use the following command to install it:
 
 
 The create process should give you a hint of the available commands available for the artemis-service.exe
+
+## Adding Runtime Dependencies
+
+Runtime dependencies like diverts, transformers, broker plugins, JDBC drivers,
+password decoders, etc. must be accessible by the broker at runtime. Package 
+the dependency in a jar, and put it on the broker's classpath. This can be done
+by placing the jar file in the `lib` directory of the broker distribution itself 
+or in the `lib` directory of the broker instance. A broker instance does not have
+a `lib` directory by default so it may need to be created.  It should be on the 
+"top" level with the `bin`, `data`, `log`, etc. directories.