Description of problem:
In plugin pack readme there are the following steps:
2. Examine the current contents of your JON Server's plugin directory:
> ls -l <JON>/jbossas/server/default/deploy/rhq.ear.rej/rhq-downloads/rhq-plugins
> dir <JON>\jbossas\server\default\deploy\rhq.ear.rej\rhq-downloads\rhq-plugins
3. Copy the new plugins from your unzipped Plugin Pack directory to the JON Server's plugin directory.
The step 3 is apparently referring to <JON>\plugins and there is not any clarifications why the step 2 has to be done. This leads user to
to copy plugin jars directly to <JON>/jbossas/server/default/deploy/rhq.ear.rej/rhq-downloads instead of <JON>/plugins
User to copy to files to <JON>/plugins
Just adding a hint for the right path to server plugins would do.
(Did we really write backslashes in the readme? )
The noted directories are correct.
JON/plugins is a shortcut, for a plugin drop box. Plugins that are put there will be copied over
to rhq.ear/rhq-downloads/rhq-plugins/ for deployment.
So it is correct to inspect the latter directory for which plugins are already there.
I just checked from the documentation for 2.4.x  and it states to use rhq.ear/rhq-downloads/rhq-plugins/ and so does the plugin pack README. The only execption for this with 2.4.x is <JON>/plugins/README.txt which states "here", so there is not issue here after all.
Documentation for 3.0.x  states to use serverRoot/jon-server-3.0.0.GA1/jbossas/server/default/deploy/rhq.ear/rhq-downloads/rhq-plugins, BUT the plugin pack README.txt states using <JON_INSTALL_DIR>/plugins and so does the <JON>/plugins/README.txt as "here".
In my opinion the path should be changed in the documentation of 3.0.x to be in line with plugin pack README.txt and the plugins drop folder README.txt.
Setting medium as per Apr 16 BZ triage