+++ 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.
git commit to master: fabce76
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 Although it makes sense that "Install Directory" use homeDir it doesn't allow the bundle to get deployed in the servers deployment directory. The server in this case is in <homeDir>/standalone/ and <homeDir>/standalone02/. The property we want is baseDir. Not sure if we should add both of these or change "Installation Directory" to "Base Directory" with the description "Base directory for server content."
git commit to master: b9ce1ee Added this: <destination-base-dir name="Base Directory" description="The base directory for server content, such as '[install-dir]/standalone' (i.e. the value found in the 'Base Directory' connection property)"> <value-context>pluginConfiguration</value-context> <value-name>baseDir</value-name> </destination-base-dir>
As this is MODIFIED or ON_QA, setting milestone to ER1.
verified on ER05