[jbosstools-issues] [JBoss JIRA] (TOOLSDOC-381) Technical Review of 7.0 Getting Started Guide

[Michelle Murray (JIRA)]

    [ https://issues.jboss.org/browse/TOOLSDOC-381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794459#comment-12794459 ] 

Michelle Murray commented on TOOLSDOC-381:
------------------------------------------

Typos fixed:
* 2.1 About Getting Started = For more information about the alternative installation *method* (> methods)
And: see *JBoss Developer Studio 7 Installation Guide and JBoss Developer Studio 7 User Guide*. (> Red Hat JBoss Developer Studio 7.0 Installation Guide and User Guide)
And: These are available at *https://access.redhat.com/site/documentation/JBoss_Developer_Studio/* (> https://access.redhat.com/site/documentation/Red_Hat_JBoss_Developer_Studio/)
* 3.1 Installation Assumptions = If you wish to install JBoss Developer Studio BYOE, *you should* follow ... (> delete)
And: the instructions in *JBoss Developer Studio 7* Installation Guide (> Red Hat JBoss Developer Studio 7.0)
* 3.2 Install JBoss Developer Studio = On Linux distributions and Microsoft Windows operating systems, *type* the path to the appropriate bit version of the Java developer kit. (> in the text field type)
And: added condition=gsg step for skipping setting up runtime detection in GSG
And: Figure 3.5. Installation Step 7: Installation Progress in *the* Finished State (> delete)
* 4.2 Tutorial Outline = Deploy the application on a runtime server using *Server Manager* (> JBoss Server Tools)
And: Add a user interface to the application that is optimized for mobile *devices* (> devices using Mobile Web Tools)
And: You *should* work through these tasks in the order they are presented because *many are prerequisites for the later tutorial tasks*. (> must; > the earlier tasks are prerequisites for the later tutorial tasks)
And: *Information* about building the complete TicketMonster application using JBoss Developer *Studio can be seen at* http://www.jboss.org/jdf/examples/get-started/ (> For information; > Studio, see <link>; > )
* 4.3 Tutorial Assumptions = JBoss Developer Studio *7* is installed. (> 7.0)
And: removed note about AS 7.1
* 5.1 Configure Maven = removed note about AS 7.1 from procedure
* 5.4 Add an Entity using Forge Tools = removed save file step as forge does this automatically
* 5.5 Add an Entity Using Hibernate Tools = *Save the Venue.java file*. (> To save the Venue.java file, press Ctrl+S.)
* 5.6 Prepare Event Records = *By default this web project uses H2 for data storage*. (> This web project uses H2 for data storage by default.)
* 5.7 Deploy the Application = The TicketMonster application can be deployed on the JBoss Enterprise Application Platform *6* server ... (> 6.x)
And: *In* the Select the server that you want to use table, (> From)
And: Figure 5.20. *Completed Run on Server Window* (> JBoss Enterprise Application Platform 6.x Selected in Run on Server Wizard)
* 5.8 Access and Query the Database = In *JBoss Developer Studio* open a new ... (> the IDE)
* 5.9 Add a RESTful Wed Service = To resolve the errors relating to missing imports, right-click anywhere in the EventService class and clickSource→*Organise* Imports. (> Organize)
                
> Technical Review of 7.0 Getting Started Guide
> ---------------------------------------------
>
>                 Key: TOOLSDOC-381
>                 URL: https://issues.jboss.org/browse/TOOLSDOC-381
>             Project: Documentation for JBoss Tools and Developer Studio
>          Issue Type: Sub-task
>      Security Level: Public(Everyone can see) 
>          Components: Getting Started Guide
>    Affects Versions: 4.1.0
>            Reporter: Michelle Murray
>            Assignee: Michelle Murray
>             Fix For: 4.1.0
>
>
> Conduct a post release technical review of 7.0 Getting Started Guide to catch any previously missed technical or copy errors.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira