Bug 672332

Summary: Session 6.1.1 describes functionality that is just supported in the EAP 4.x plug-in
Product: [Other] RHQ Project Reporter: Bruno Machado <bmachado>
Component: DocumentationAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED CURRENTRELEASE QA Contact: Mike Foley <mfoley>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0.0CC: dlackey, rsoares, skondkar
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-02 03:16:01 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Bruno Machado 2011-01-24 15:50:33 EST
Session 6.1.1. Deploying EAR and WAR documentation says:
"The path to the directory to which to deploy the EAR or WAR package. The destination directory is relative to the JBoss server instance installation directory; this cannot contain an absolute path or go up a parent directory."

This functionality is not supported in the EAP 5.x plug-in. There is no path option to deploy it.

Some customers are complaining because they were expecting the same behaviour in both plug-ins.

It should be good to describe that the functionality is not supported in all plug-ins.

To see the full documentation, access:
Comment 1 Deon Ballard 2011-07-01 15:13:21 EDT
Apologies; two different bugs were filed about the same issue, and I neglected to update this one.

The section now explicitly says that it is for EAP 4 only.

Comment 2 Sunil Kondkar 2011-07-04 04:29:23 EDT
Verified that the section 6.1.1 displays the note "This is only an option for EAP 4.x instances. It is not supported for EAP 5.x."
Comment 3 Heiko W. Rupp 2013-09-02 03:16:01 EDT
Bulk closing of issues that were VERIFIED, had no target release and where the status changed more than a year ago.