JDF-439 Updated TicketMonster tutorial to use JBDS 7

tutorial/Introduction.asciidoc

@@ -30,15 +30,15 @@ In this tutorial, we will cover the following topics:
 - Using the Mobile BrowserSim
 
 [[jbds5_mobile_browsersim_image]]
-.JBoss Developer Studio 6 with Mobile BrowserSim
-image::gfx/introduction/jbds6_mobile_browsersim.png[]
+.JBoss Developer Studio 7 with Mobile BrowserSim
+image::gfx/introduction/jbds7_mobile_browsersim.png[]
 
 == Installation
 
 
-The first order of business is to get your development environment setup and JBoss Developer Studio v6 installed. JBoss Developer Studio is Eclipse Juno (4.2 SR2) for Java EE Developers plus select JBoss Tools and is available for free. Visit https://devstudio.jboss.com/download/6.x.html to download it.  You may also choose to install JBoss Tools 4.0.1 into your existing Eclipse for Java EE Developers installation. This document uses screenshots depicting JBoss Developer Studio.
+The first order of business is to get your development environment setup and JBoss Developer Studio v7 installed. JBoss Developer Studio is Eclipse Kepler (e4.3) for Java EE Developers plus select JBoss Tools and is available for free. Visit https://devstudio.jboss.com/download/7.x.html to download it.  You may also choose to install JBoss Tools 4.1 into your existing Eclipse for Java EE Developers installation. This document uses screenshots depicting JBoss Developer Studio.
 
-You must have a Java Development Kit (JDK) installed, either v6 or v7 will work - whilst a JVM runtime will work for most use cases, for a developer environment it is normally best to have the full JDK. System requirements for JBoss Developer Studio are listed in the System Requirements chapter of the link:https://access.redhat.com/site/documentation/en-US/JBoss_Developer_Studio/6.0/html/Getting_Started_Guide/minimumrequirements.html[JBoss Developer Studio 6.0 Getting Started Guide] online documentation.
+You must have a Java Development Kit (JDK) installed, either v6 or v7 will work - whilst a JVM runtime will work for most use cases, for a developer environment it is normally best to have the full JDK. System requirements for JBoss Developer Studio are listed in the System Requirements chapter of the link:https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Developer_Studio/7.0/html/Installation_Guide/chap-System_Requirements.html[JBoss Developer Studio 7.0 Installation Guide] online documentation.
 
 [TIP]
 ==============================================================
@@ -49,24 +49,27 @@ To see JBoss Tools being installed into Eclipse, see
 link:http://vimeo.com/39743315[this video].
 ==============================================================
 
-The JBoss Developer Studio installer has a (very long!) name such as `jbdevstudio-product-universal-6.0.1.GA-v20130327-2052-B361.jar`
+The JBoss Developer Studio installer has a (very long!) name such as `jbdevstudio-product-universal-7.0.0.GA-v20130720-0044-B364.jar`
 where the latter portion of the file name relates to build date and version information and the text near the front related to the target operating system. The "universal" installer is for any operating system.  To launch the installer you may simply be able to double-click on the .jar file name or you may need to issue the following from the operating system command line:
 
-    java -jar jbdevstudio-product-universal-6.0.1.GA-v20130327-2052-B361.jar
+    java -jar jbdevstudio-product-universal-7.0.0.GA-v20130720-0044-B364.jar
 
 We recommend using the "universal" installer as it handles Windows, Mac OS X and Linux - 32-bit and 64-bit versions.
 
 [NOTE]
 ===============================================================
 Even if you are installing on a 64-bit OS, you may still wish 
 to use the 32-bit JVM for the JBoss Developer Studio (or 
-Eclipse + JBoss Tools). Only the 32-bit version provides the
-Visual Page Editor - a split-pane editor that gives you a 
-glimpse of what your HTML/XHTML (JSF, JSP, etc) will look like.
+Eclipse + JBoss Tools). Only the 32-bit version provides a
+supported version of the Visual Page Editor - a split-pane 
+editor that gives you a glimpse of what your HTML/XHTML (JSF,
+ JSP, etc) will look like.
 Also, the 32-bit version uses less memory than the 64-bit 
 version. You may still run your application server in 64-bit 
 JVMs if needed to insure compatibility with the production
 environment whilst keeping your IDE in 32-bit mode.
+Visual Page Editor has experimental support for 64-bit JVMs in JBoss 
+Developer Studio 7. Please refer https://community.jboss.org/wiki/JBosstoolsVisualEditorFAQ[the JBoss Tools Visual Editor FAQ] for details.
 ===============================================================
 
 [[installer-wizard_image]]
@@ -102,7 +105,7 @@ the last icon, on the last row - assuming you are in the JBoss
 Perspective.
 =================================================================
 
-First, select *Create Projects -> Java EE Web Project* in JBoss Central. Under the covers, this uses a Maven archetype which creates a Java EE 6 web application (.war), based around Maven.  The project can be built outside of the IDE, and in continuous integration solutions like Hudson/Jenkins.
+First, select *Start from scratch -> Java EE Web Project* in JBoss Central. Under the covers, this uses a Maven archetype which creates a Java EE 6 web application (.war), based around Maven.  The project can be built outside of the IDE, and in continuous integration solutions like Hudson/Jenkins.
 
 [[jboss-central_image]]
 .JBoss Central
@@ -205,7 +208,7 @@ The `pom.xml` editor has several tabs along its bottom edge.
 
 [[pom_xml_tabs_image]]
 .pom.xml Editor Tabs
-image::gfx/introduction/pom_xml_tabs.png[scaledwidth="90%"]
+image::gfx/introduction/pom_xml_tabs.png[]
 
 For this tutorial, we do not need to edit the `pom.xml` as it already provides the Java EE 6 APIs that we will need (e.g. JPA, JAX-RS, CDI). You should spend some time exploring the *Dependencies* and the *pom.xml* (source view) tabs.   
 
@@ -319,7 +322,7 @@ The first time you start Forge, you will be prompted with a *Forge Not Running*
 
 [[forge_is_not_running_image]]
 .Show Forge Not Running
-image::gfx/introduction/forge_is_not_running.png[scaledwidth="70%"]
+image::gfx/introduction/forge_is_not_running.png[]
 
 [TIP]
 ==============================================================================
@@ -389,7 +392,7 @@ You should end up with the command `field string --named name`, to execute it, p
 
 [[forge_added_name_image]]
 .@Column name
-image::gfx/introduction/forge_added_name.png[scaledwidth="90%"]
+image::gfx/introduction/forge_added_name.png[]
 
 From this point forward, we will assume you have the basics of using Forge's interactive command line. The remaining commands to run are:
 
@@ -488,7 +491,7 @@ The next step in the wizard will provide a sampling of the refactored sources 
 
 [[hibernate_add_jpa_annotations_step2_image]]
 .Hibernate: add JPA annotations Step 2
-image::gfx/introduction/hibernate_add_jpa_annotations_step2.png[scaledwidth="80%"]
+image::gfx/introduction/hibernate_add_jpa_annotations_step2.png[]
 
 Select *Finish*.