Bug 245227 - JBoss AS Documentation index page has three links to Getting Started Guide - same book
JBoss AS Documentation index page has three links to Getting Started Guide - ...
Status: CLOSED CURRENTRELEASE
Product: JBoss Enterprise Application Platform 4
Classification: JBoss
Component: doc-Getting_Started_Guide (Show other bugs)
4.2.0
All Linux
high Severity medium
: ---
: ---
Assigned To: Joshua Wulf
: Documentation
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-06-21 15:25 EDT by Shelly McGowan
Modified: 2014-10-19 18:56 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-08-03 21:19:08 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Shelly McGowan 2007-06-21 15:25:30 EDT
Description of problem:


In JBEAP RC7 distribution, the Documentation index has three Getting Started
Guide Links:

From UI:

 JBoss Enterprise Application Platform Documentation

    *

      JBoss Enterprise Application Platform Installation Guide

      Getting Started Guide

      Getting Started Guide
    *

      Getting Started Guide
    *

      Server Configuration Guide
    *

      Clustering Guide



index.html source:

        <p>
     <a href="Getting_Started.pdf">Getting Started Guide</a>
                                </p>
            <p>
     <a href="Getting_Started.pdf">Getting Started Guide</a>
                                </p>
          </li>
          <li>
            <p>
     <a href="Getting_Started.pdf">Getting Started Guide</a>
                                </p>
Comment 1 Joshua Wulf 2007-06-22 02:29:15 EDT
Fixed and pushing through tonight.
Comment 2 Joshua Wulf 2007-06-22 04:31:44 EDT
Can QA please confirm this in a post-RC7 docs spin.
Comment 3 Shelly McGowan 2007-06-22 07:38:25 EDT
Sure

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