Bug 843629 - Bug in JBoss Getting Started Guide
Summary: Bug in JBoss Getting Started Guide
Keywords:
Status: VERIFIED
Alias: None
Product: JBoss Enterprise Application Platform 5
Classification: JBoss
Component: doc-Getting_Started_Guide
Version: 5.1.2
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact: Chuck Copello
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-26 19:40 UTC by Joshua Wilson
Modified: 2023-05-15 18:03 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Joshua Wilson 2012-07-26 19:40:21 UTC
Description of problem: Bad link to Admin doc.


Version-Release number of selected component (if applicable):


How reproducible: go to 1.2.1. Start the Server 
http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/Getting_Started_Guide/Starting_and_Stopping_the_Server.html#Starting_and_Stopping_the_Server-Start_the_Server
The link to the Administration and Configuration Guide points to 
http://www.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5.0.0/html-single/Administration_And_Configuration_Guide/index.html
and it should point to
http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html-single/Administration_And_Configuration_Guide/index.html

I believe that the version went from 5.0.0 to just 5.


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Russell Dickenson 2013-01-07 03:18:21 UTC
I have checked the current version of this book, available at [1], and confirmed that the link mentioned above is now correct.

[1] http://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/Getting_Started_Guide/Starting_and_Stopping_the_Server.html

Comment 2 Chuck Copello 2017-02-21 18:52:05 UTC
Link corrected in 2013; marking Verified.


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