Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 957288

Summary: Add EAP base/home directory bundle target to EAP 6 plug-in
Product: [JBoss] JBoss Operations Network Reporter: Larry O'Leary <loleary>
Component: Plugin -- JBoss EAP 6Assignee: John Mazzitelli <mazz>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: high Docs Contact:
Priority: high    
Version: JON 3.1.2CC: ccrouch, hrupp, loleary, lzoubek, mazz
Target Milestone: ER01Keywords: FutureFeature
Target Release: JON 3.2.0   
Hardware: All   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 957282
: 958980 (view as bug list) Environment:
Last Closed: Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 957282    
Bug Blocks: 958980    

Description Larry O'Leary 2013-04-26 21:08:29 UTC 
+++ 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.
Comment 1 John Mazzitelli 2013-04-29 15:16:08 UTC 
git commit to master: fabce76
Comment 2 Larry O'Leary 2013-05-16 00:08:17 UTC 
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."
Comment 3 John Mazzitelli 2013-05-16 17:12:23 UTC 
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>
Comment 4 Larry O'Leary 2013-09-06 14:31:32 UTC 
As this is MODIFIED or ON_QA, setting milestone to ER1.
Comment 5 Libor Zoubek 2013-11-18 17:29:05 UTC 
verified on ER05