Bug 724335 (BRMS-280) - broken link on BRMS Userguide
Summary: broken link on BRMS Userguide
Keywords:
Status: CLOSED NEXTRELEASE
Alias: BRMS-280
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: Documentation
Version: 5.0.1
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: 5.0.2
Assignee: Len DiMaggio
QA Contact:
URL: http://jira.jboss.org/jira/browse/BRM...
Whiteboard:
Depends On:
Blocks: BRMS-285
TreeView+ depends on / blocked
 
Reported: 2010-03-23 19:05 UTC by Jehudi Castro Sierra
Modified: 2013-01-11 02:16 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-04-21 11:31:45 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker BRMS-280 0 Minor Closed broken link on BRMS Userguide 2013-02-08 10:19:16 UTC

Description Jehudi Castro Sierra 2010-03-23 19:05:27 UTC
Date of First Response: 2010-03-31 10:56:36
securitylevel_name: Public

In the page 10 of the BRMS_Userguide.pdf documment there is this broken link:
http://www.jboss.com/products/platforms/brms/testedconfigurations/
(404 - Page Not Found)

Comment 1 Len DiMaggio 2010-03-30 14:09:50 UTC
Link: Added: This issue depends BRMS-285


Comment 2 Len DiMaggio 2010-03-31 14:56:36 UTC
The correct URL is:

http://www.jboss.com/products/platforms/brms/supportedconfigurations/



Comment 3 Len DiMaggio 2010-04-05 11:36:52 UTC
Link: Removed: This issue depends BRMS-285 


Comment 4 Len DiMaggio 2010-04-05 11:37:19 UTC
Link: Added: This issue is a dependency of BRMS-285


Comment 5 Dana Mison 2010-04-06 06:31:01 UTC
fixed URL, checked in

Comment 7 Dana Mison 2010-04-19 05:24:05 UTC
I didn't realise that there were more than one URL being referred to here.  There was a build issue that prevented the first one I updated from appearing which is what I thought was being referred to.

Both fixed now.

Comment 9 Dana Mison 2010-04-20 05:53:24 UTC
updated


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