Bug 1154074
| Summary: | Datasource description in installer points to old documentation | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Nikoleta Hlavickova <nziakova> |
| Component: | Installer | Assignee: | jboss-set |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Petr Kremensky <pkremens> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.4.0 | CC: | kkhan |
| Target Milestone: | DR8 | ||
| Target Release: | EAP 6.4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-08-19 12:44:15 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Nikoleta Hlavickova
2014-10-17 13:02:04 UTC
I think for this issue, it's better to change our link to https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/ instead of the link we're currently using. Does this sound good Nikoleta? Nikoleta is right. The 'JBoss Enterprise Application Platform' guides are being renamed to 'Red Hat JBoss Enterprise Application Platform' for 6.4. I believed the URL in comment 2 is correct. Thomas, if you have room, you can use the basic URL, but specify the book and section, for example: If your driver is not supported, see the 'Datasource Configuration' section of the `Administration and Configuration Guide' for Red Hat JBoss Enterprise Application Platform [located here: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Enterprise_Application_Platform/]. If you don't have the space, you could turn the 'Administration and Configuration Guide' into a link. Tom or Russell, do you know if the above links are correct or do you have a better suggestion? I've changed the link to be https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Enterprise_Application_Platform/ . Note that this does not work yet since the Documentation is not staged. Hey Tom I believe this could be moved to ON_QA. I don't think we should point the link from 'Admininstration and Configuration Guide' to https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Enterprise_Application_Platform/ since it points to documentation index page not to A&C guide itself (the screen similar to https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/). --------------------------------- ... You can find examples for major databases in the 'Datasource Configuration' section of the EAP documentation, which can serve as a template for your definition. EAP Documentation - [Admininstration and Configuration Guide|https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Enterprise_Application_Platform/] --------------------------------- how about --------------------------------- ... You can find examples for major databases in the 'Datasource Configuration' section of the Administration and Configuration Guide, which can serve as a template for your definition. [EAP Documentation|https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Enterprise_Application_Platform/] --------------------------------- Agreed Petr, will update the link for DR13. Also I was told that we shouldn't be linking to chapters directly, but to the index page. Do you have any comments, Sande? Thomas, that is my understanding. We point them to the chapter or section. Tom Wells, can you verify the above and also what the link for the JBoss EAP 6.4 documentation will be? I've updated the string with another interim message until we get some feedback :) Verified on EAP 6.4.0.DR13. Hey Tom, I was just using jira syntax for making links, I wasn't trying to force you to use "|" as separator :), but I guess we can stay like this. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |