Back-port this feature/request to the latest 3.1.x release. +++ This bug was initially created as a clone of JBoss ON 3.2 Bug #957288 +++ +++ This bug was initially created as a clone of Bug #957282 +++ had discussions with larry l, charles c and alan s. came to the conclusion we should support the same bundle target that the other jboss plugins support - being able to deploy anywhere under the base install dir of the AS installation. --- Additional comment from John Mazzitelli on 2013-04-26 16:22:40 EDT --- we want to add something like this: <bundle-target> <destination-base-dir name="Install Directory" description="The top directory where the application server is installed."> <value-context>pluginConfiguration</value-context> <value-name>homeDir</value-name> </destination-base-dir> </bundle-target> We can keep the original destination-base-dir in here if we want (keeping the metric "deploy dir" target) and add any others we want in the future. --- Additional comment from John Mazzitelli on 2013-04-29 11:16:08 EDT --- git commit to master: fabce76
Committed to release/jon3.1.x as https://git.fedorahosted.org/cgit/rhq/rhq.git/commit/?id=a214605ec9abd53cc20b0a3eeeed34465b54e9f1 commit a214605ec9abd53cc20b0a3eeeed34465b54e9f1 Author: John Mazzitelli <mazz> Date: Mon Apr 29 11:15:34 2013 -0400 BZ 957282 957288 add bundle target of "Install Directory" (cherry picked from commit fabce7666b08f73ea113807ec42b47a3d3eb5929)
Test failed. The deployment does not end up in the standalone installation but instead is rooted at JBOSS_HOME. The expectation was to specify the deployment directory as the path prefix. For example: deployments/my-bundle-dest.war
Committed to release/jon3.1.x as https://git.fedorahosted.org/cgit/rhq/rhq.git/commit/?id=79cf09367563622891b75d5f0f06f4b86d14a5d2 commit 79cf09367563622891b75d5f0f06f4b86d14a5d2 Author: John Mazzitelli <mazz> Date: Thu May 16 13:11:14 2013 -0400 BZ 957282 957288 add bundle target of "Base Directory" (cherry picked from commit b9ce1ee3cc01fd2bf5614f10e164a1f4cebfe42c)
Closing as there will not be a 3.1.3 release. This is being tracked for 3.2 in the 'depends on' field.