[jbosstools-issues] [JBoss JIRA] (TOOLSDOC-449) Update explicit 7.1 text and figs references in docs for 8.0

[Michelle Murray (JIRA)]

     [ https://issues.jboss.org/browse/TOOLSDOC-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michelle Murray updated TOOLSDOC-449:
-------------------------------------

    Description: 
_Text_

*Installation Guide*
2.2 Supported Operating Systems and Architectures
2.3 Computer Memory
2.4 Compatible Java Developer Kits
3.2 Install JBoss Developer Studio
3.3 Install JBoss Developer Studio BYOE
5.2 Upgrade from JBoss Developer Studio 6.x and Earlier
5.3 Upgrade from JBoss Developer Studio 7.0
B.1 Build the Universal Installer from Source

*Getting Started Guide*
2.1 About Getting Started
3.1 Installation Assumptions
3.2 Install JBoss Developer Studio (shared with Install)
4.3 Tutorial Assumptions

*Migration Guide*
2.2 Upgrade from JBoss Developer Studio 6.x and Earlier (shared with Install)
2.3 Upgrade from JBoss Developer Studio 7.0 (shared with Install)
3.1 Change the Version of Eclipse Being Used with JBoss Developer Studio BYOE

*User Guide*
--

_Figures_
*Installation Guide*
3.2 Installation Step 3: Select Target Folder (make sure to miss off top bar of window else get Beta1 identifier)
3.3 Installation Step 4: Select Java VM (make sure to miss off top bar of window else get Beta1 identifier)
3.4 Add Location Window for Runtime Detection (should be EAP6.2.2)
3.5 Installation Step 7: Installation Progress in Finished State (make sure to miss off top bar of window else get Beta1 identifier)
3.6 Install JBoss Developer Studio BYOE via Eclipse Marketplace
3.7 Confirm Selected Features Window
3.10 Work from an Online Website
3.11 Work from a Local Copy of the Update .zip file
3.12 Available Software Window Listing JBoss Developer Studio 7.x - Bring Your Own Eclipse
4.4 One New Application Server Found by Runtime Detection (should be EAP6.2.2)
6.2 Uninstall JBoss Developer Studio via Eclipse Marketplace
6.3 Confirm Selected Features Window

*Getting Started Guide*
3.2 Installation Step 3: Select Target Folder (shared with Install)
3.3 Installation Step 4: Select Java VM (shared with Install)
3.4 Installation Step 7: Installation Progress in Finished State (shared with Install)
5.2. Add Maven Repository Window (should be EAP6.2.2)
5.4. JBoss Enterprise Application Platform 6.x Found by Runtime Detection (should be EAP6.2.2)
5.5. JBoss Enterprise Application Platform 6.x Server Listed in Servers View (should be EAP6.2.2)
5.7. JBoss Enterprise Application Platform 6.x Selected as Target Runtime in Java EE Web Project Wizard (should be EAP6.2.2)

*Migration Guide*
--

*User Guide*
2.5 JBoss Buzz
2.23 Work from a Local Copy of the JBoss Central .zip File

  was:
_Text_

*Installation Guide*
2.2 Supported Operating Systems and Architectures
2.3 Computer Memory
2.4 Compatible Java Developer Kits
3.2 Install JBoss Developer Studio
3.3 Install JBoss Developer Studio BYOE
5.2 Upgrade from JBoss Developer Studio 6.x and Earlier
5.3 Upgrade from JBoss Developer Studio 7.0
B.1 Build the Universal Installer from Source

*Getting Started Guide*
2.1 About Getting Started
3.1 Installation Assumptions
3.2 Install JBoss Developer Studio (shared with Install)
4.3 Tutorial Assumptions

*Migration Guide*
2.2 Upgrade from JBoss Developer Studio 6.x and Earlier (shared with Install)
2.3 Upgrade from JBoss Developer Studio 7.0 (shared with Install)
3.1 Change the Version of Eclipse Being Used with JBoss Developer Studio BYOE

*User Guide*
--

_Figures_
*Installation Guide*
3.2 Installation Step 3: Select Target Folder
3.3 Installation Step 4: Select Java VM
3.4 Add Location Window for Runtime Detection (should be EAP6.2.2)
3.5 Installation Step 7: Installation Progress in Finished State
3.6 Install JBoss Developer Studio BYOE via Eclipse Marketplace
3.7 Confirm Selected Features Window
3.10 Work from an Online Website
3.11 Work from a Local Copy of the Update .zip file
3.12 Available Software Window Listing JBoss Developer Studio 7.x - Bring Your Own Eclipse
4.4 One New Application Server Found by Runtime Detection (should be EAP6.2.2)
6.2 Uninstall JBoss Developer Studio via Eclipse Marketplace
6.3 Confirm Selected Features Window

*Getting Started Guide*
3.2 Installation Step 3: Select Target Folder (shared with Install)
3.3 Installation Step 4: Select Java VM (shared with Install)
3.4 Installation Step 7: Installation Progress in Finished State (shared with Install)
5.2. Add Maven Repository Window (should be EAP6.2.2)
5.4. JBoss Enterprise Application Platform 6.x Found by Runtime Detection (should be EAP6.2.2)
5.5. JBoss Enterprise Application Platform 6.x Server Listed in Servers View (should be EAP6.2.2)
5.7. JBoss Enterprise Application Platform 6.x Selected as Target Runtime in Java EE Web Project Wizard (should be EAP6.2.2)

*Migration Guide*
--

*User Guide*
2.5 JBoss Buzz
2.23 Work from a Local Copy of the JBoss Central .zip File


    
> Update explicit 7.1 text and figs references in docs for 8.0
> ------------------------------------------------------------
>
>                 Key: TOOLSDOC-449
>                 URL: https://issues.jboss.org/browse/TOOLSDOC-449
>             Project: Documentation for JBoss Tools and Developer Studio
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Getting Started Guide, Installation Guide, Migration Guide, User Guide
>            Reporter: Michelle Murray
>            Assignee: Suz Dorfield
>             Fix For: 4.2.0.Beta1
>
>   Original Estimate: 1 day, 30 minutes
>          Time Spent: 40 minutes
>  Remaining Estimate: 7 hours, 50 minutes
>
> _Text_
> *Installation Guide*
> 2.2 Supported Operating Systems and Architectures
> 2.3 Computer Memory
> 2.4 Compatible Java Developer Kits
> 3.2 Install JBoss Developer Studio
> 3.3 Install JBoss Developer Studio BYOE
> 5.2 Upgrade from JBoss Developer Studio 6.x and Earlier
> 5.3 Upgrade from JBoss Developer Studio 7.0
> B.1 Build the Universal Installer from Source
> *Getting Started Guide*
> 2.1 About Getting Started
> 3.1 Installation Assumptions
> 3.2 Install JBoss Developer Studio (shared with Install)
> 4.3 Tutorial Assumptions
> *Migration Guide*
> 2.2 Upgrade from JBoss Developer Studio 6.x and Earlier (shared with Install)
> 2.3 Upgrade from JBoss Developer Studio 7.0 (shared with Install)
> 3.1 Change the Version of Eclipse Being Used with JBoss Developer Studio BYOE
> *User Guide*
> --
> _Figures_
> *Installation Guide*
> 3.2 Installation Step 3: Select Target Folder (make sure to miss off top bar of window else get Beta1 identifier)
> 3.3 Installation Step 4: Select Java VM (make sure to miss off top bar of window else get Beta1 identifier)
> 3.4 Add Location Window for Runtime Detection (should be EAP6.2.2)
> 3.5 Installation Step 7: Installation Progress in Finished State (make sure to miss off top bar of window else get Beta1 identifier)
> 3.6 Install JBoss Developer Studio BYOE via Eclipse Marketplace
> 3.7 Confirm Selected Features Window
> 3.10 Work from an Online Website
> 3.11 Work from a Local Copy of the Update .zip file
> 3.12 Available Software Window Listing JBoss Developer Studio 7.x - Bring Your Own Eclipse
> 4.4 One New Application Server Found by Runtime Detection (should be EAP6.2.2)
> 6.2 Uninstall JBoss Developer Studio via Eclipse Marketplace
> 6.3 Confirm Selected Features Window
> *Getting Started Guide*
> 3.2 Installation Step 3: Select Target Folder (shared with Install)
> 3.3 Installation Step 4: Select Java VM (shared with Install)
> 3.4 Installation Step 7: Installation Progress in Finished State (shared with Install)
> 5.2. Add Maven Repository Window (should be EAP6.2.2)
> 5.4. JBoss Enterprise Application Platform 6.x Found by Runtime Detection (should be EAP6.2.2)
> 5.5. JBoss Enterprise Application Platform 6.x Server Listed in Servers View (should be EAP6.2.2)
> 5.7. JBoss Enterprise Application Platform 6.x Selected as Target Runtime in Java EE Web Project Wizard (should be EAP6.2.2)
> *Migration Guide*
> --
> *User Guide*
> 2.5 JBoss Buzz
> 2.23 Work from a Local Copy of the JBoss Central .zip File

--
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