Bug 1011456 - [Doc Bug Fix] Add information about crippled JARs after patching
Summary: [Doc Bug Fix] Add information about crippled JARs after patching
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Documentation
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ER7
: EAP 6.3.0
Assignee: Nichola Moore
QA Contact: Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-24 10:28 UTC by Jan Martiska
Modified: 2014-08-14 15:25 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Build Name: 14873, Installation Guide-6.2-1 Build Date: 18-09-2013 14:19:43 Topic ID: 13441-507286 [Latest]
Last Closed: 2014-06-28 15:41:48 UTC
Type: Bug


Attachments (Terms of Use)

Comment 3 Scott Mumford 2014-05-29 03:09:08 UTC
Classifying this as a [Doc Bug Fix] ticket under the assumption that the current patching documentation needs to have a mention of the crippling of jars added.

Should the rest of the details outlined in the description be required, this ticket should be reclassified as a [Doc Feature].

Comment 4 Nichola Moore 2014-06-04 05:18:54 UTC
I have added an "Important" box to topic 13441. I've mentioned the changed directory structure without going in to too much detail, and I've added the information about the 'crippled' jars. I felt it was important to point out, given what was mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1011456#c0 above, that the proper rollback procedure should be followed to enable the original module jars to be enabled. 

Topic changed:

13441 revision 650930

Comment 6 Jan Martiska 2014-06-10 08:35:29 UTC
Looks very good, thanks.


Note You need to log in before you can comment on or make changes to this bug.