Bug 1018684 - Migration guide contains topic that failed validation and the Compiler Output
Summary: Migration guide contains topic that failed validation and the Compiler Output
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: GA
: EAP 6.3.0
Assignee: sgilda
QA Contact: Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-14 07:48 UTC by Nikoleta Hlavickova
Modified: 2014-08-14 15:19 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-28 15:28:19 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Nikoleta Hlavickova 2013-10-14 07:48:49 UTC 
Section 3.2.15.3. Modify Client Applications contains only error box with the following text:

Topic 11567 failed validation and is not included in this build.
Please review the compiler error for Topic ID 11567 for more detailed information. 

This error probably generated Chapter 5. Compiler Output that should not be included in the Migration Guide.
Comment 1 Nikoleta Hlavickova 2013-10-14 07:50:06 UTC 
URLs of the invalid section and the redundant chapter:

http://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/6.2/html-single/Migration_Guide/index.html#sect-Migrate_Spring_Applications

http://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/6.2/html-single/Migration_Guide/index.html#idm15429896
Comment 2 sgilda 2014-04-15 17:48:17 UTC 
This was fixed a some point. See:

https://access.redhat.com/site/documentation/en-US/JBoss_Enterprise_Application_Platform/6.2/html-single/Migration_Guide/index.html#Modify_Client_Applications
Comment 3 Nikoleta Hlavickova 2014-04-24 12:28:42 UTC 
Verified with EAP 6.3.0 ER2, revision 6.3.0-8
Note You need to log in before you can comment on or make changes to this bug.