Description of problem: Deploy a bundle with a WAR archive to JBoss AS 7 standalone server leads to wrong directory. How reproducible: Steps to Reproduce: 1.Make an Ant bundle with a simple WAR archive within. 2.Update the bundle file to RHQ to create a new bundle. 3.New a group with JBoss AS 7 standalone server 4.Deploy the bundle to the created group. Actual results: The WAR is deployed correctly at <JBoss Standalone Server>/standalone/deployments/ Expected results: The WAR is deployed at <JBoss Standalone Server>/standalone/deployment/<Destination Directory> Additional info: This should be a typo.
master 264bf23cb1
*** Bug 843868 has been marked as a duplicate of this bug. ***
Created attachment 604660 [details] CLI-script to fix the plugin property for the bundle deployment directory
This value should not be hard-coded as this is configurable and could change. In my opinion, this should be a trait. 'deployments' is only the value provided in the example configuration and is not intended to the the absolute directory name. Instead, we should read the value from the deployment-scanner module and re-read this value from time to time to ensure it gets updated.
A new implementation using a trait is now pushed to master as 1ace95e The plugin config 'deployDir' has been removed, so on plugin upgrade users will get the correct setting. Todo QA: test deploying a bundle after plugin upgrade to a server that was in inventory before the upgrade to see if the <bundle-destination> metadata is correctly updated.
Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since.