Bug 1040117

Summary: Getting product name into folder structure for layered products
Product: [JBoss] JBoss Data Virtualization 6 Reporter: Catherine Robson <crobson>
Component: ProductizationAssignee: Julian Coleman <jcoleman>
Status: CLOSED WONTFIX QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.0.0CC: asantos, atangrin, felias
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-14 15:00:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Catherine Robson 2013-12-10 18:45:42 UTC
Description of problem:
When using the layered product model, we're having the folder name of what we install always default to jboss-eap-6.x.  For users, this is misleading and confusing for them to identify what is actually installed (Just EAP?  FSW on EAP?  BRMS and FSW on EAP?).  See if we can come up with a solution that starts to include product named folders to make this easier on users.

Some thoughts that were in e-mails:

One option is:
/INSTALL DIR
  /jboss-eap-6.1.1
  /FSW
    /bin/launch-eap-with-fsw-config.sh
    /documentation
    /quickstarts
  /BRMS 
    /see above

Or, It probably doesn’t even need to be shared 

- e.g. for windows.

c:/

/jboss-eap-6.1.1

/fsw

/brms




Related bugs for other layered products that also need to solve this in comments - we should solve this consistently across layered products.

Comment 3 Anne-Louise Tangring 2013-12-17 14:12:34 UTC
This can't be fixed because the structure is laid down by EAP. EAP has always had the EAP part at the top. It's likely that the EAP patching would break and we're not sure that it wont' hurt us in the future if we change this.

Comment 5 belong 2014-01-08 03:33:33 UTC
Assuming this does not need to be documented as a known issue in the Release Notes - setting to requires_doc_text- accordingly.