Bug 900748 (JBPAPP6-874) - JBoss EAP 6.0.0GA jar installer is missing jboss-client.jar
Summary: JBoss EAP 6.0.0GA jar installer is missing jboss-client.jar
Keywords:
Status: CLOSED DUPLICATE of bug 2040112
Alias: JBPAPP6-874
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Installer
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: EAP 6.0.1
Assignee: Danesh Mondegarian
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBP...
Whiteboard: eap6
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-31 13:47 UTC by Nikhil Mone
Modified: 2013-11-30 15:20 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
All OS
Last Closed: 2012-11-07 14:45:54 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBPAPP6-874 0 Major Closed JBoss EAP 6.0.0GA jar installer is missing jboss-client.jar 2013-05-14 15:19:40 UTC

Description Nikhil Mone 2012-07-31 13:47:14 UTC 
Affects: Compatibility/Configuration
Help Desk Ticket Reference: https://na7.salesforce.com/500A000000A7PmYIAV
Steps to Reproduce: Download EAP 6.0.0 GA jar installer from customer portal and install it.
Workaround: Workaround Exists
Workaround Description: Use zip installer instead.
project_key: JBPAPP6

JBoss EAP 6.0.0GA jar installer is missing jboss-client.jar, however the zip installer has the jar.

The jar is missing from below directory :

jboss-eap-6.0.0_GA/bin/client/
Comment 1 Thomas Hauser 2012-07-31 14:43:05 UTC 
Issue will be fixed in 6.0.1
Comment 2 Madhumita Sadhukhan 2012-10-01 09:43:56 UTC 
Verified that jboss-client.jar exists within installed EAP for 6.0.1.ER2 after installing from installer jar
Comment 3 Misty Stanley-Jones 2012-11-05 05:28:53 UTC 
Release Notes Docs Status: Added: Not Required
Comment 4 Anne-Louise Tangring 2012-11-13 20:07:42 UTC 
Release Notes Docs Status: Removed: Not Required 
Docs QE Status: Removed: NEW
Note You need to log in before you can comment on or make changes to this bug.