From jbosstools-commits at lists.jboss.org Tue Sep 23 04:56:08 2008
Content-Type: multipart/mixed; boundary="===============2313568017653457278=="
MIME-Version: 1.0
From: jbosstools-commits at lists.jboss.org
To: jbosstools-commits at lists.jboss.org
Subject: [jbosstools-commits] JBoss Tools SVN: r10403 -
 trunk/documentation/guides/GettingStartedGuide/en/modules.
Date: Tue, 23 Sep 2008 04:56:08 -0400
Message-ID: <E1Ki3gm-0000W7-FL@committer01.frg.pub.inap.atl.jboss.com>

--===============2313568017653457278==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

Author: ochikvina
Date: 2008-09-23 04:56:08 -0400 (Tue, 23 Sep 2008)
New Revision: 10403

Modified:
   trunk/documentation/guides/GettingStartedGuide/en/modules/getting_starte=
d.xml
Log:
https://jira.jboss.org/jira/browse/JBDS-420 - correcting the note.

Modified: trunk/documentation/guides/GettingStartedGuide/en/modules/getting=
_started.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/documentation/guides/GettingStartedGuide/en/modules/getting_start=
ed.xml	2008-09-23 07:50:56 UTC (rev 10402)
+++ trunk/documentation/guides/GettingStartedGuide/en/modules/getting_start=
ed.xml	2008-09-23 08:56:08 UTC (rev 10403)
@@ -67,12 +67,16 @@
 export PATH=3D$PATH:$JAVA_HOME/bin]]></programlisting>
     </listitem>
    </itemizedlist>
+
    <note>
     <title>Note:</title>
-    <para>When you add $JAVA_HOME/bin to $PATH, you should add it <emphasi=
s role=3D"bold"
-     >before</emphasis> the old $PATH not after it. This way, the machine =
will pick up the new JVM
-     first. You only need to run &quot;alternative&quot; as a safe guard f=
or the right
-    JVM.</para>
+
+    <para>=EF=BB=BFIf you have JDK already installed and added in your sys=
tem path, you should add
+     <emphasis>$JAVA_HOME/bin</emphasis> before the old <emphasis>$PATH</e=
mphasis> (not after it) so that the new
+     version of JDK can be found first, i. e. <para>
+      <emphasis>export PATH=3D$JAVA_HOME/bin:$PATH</emphasis>
+     </para> This way, the machine will pick up the new JVM first. You onl=
y need to run
+     "alternative" as a safe guard for the right JVM. </para>
    </note>
 =

    <para>Set this variable for your account doing the installation and als=
o for the user account
@@ -386,13 +390,14 @@
      </listitem>
     </itemizedlist>
 =

-    <para>Some of our newer plugins, like TPTP and BIRT, need additional d=
rivers. On the left side of the download page =

-     you can find all of the required drivers for chosen build and their v=
ersions.</para>
+    <para>Some of our newer plugins, like TPTP and BIRT, need additional d=
rivers. On the left side
+     of the download page you can find all of the required drivers for cho=
sen build and their
+     versions.</para>
     <para>Instead of downloading the nightly build version manually, it&ap=
os;s also possible to
      get the latest release of <property>JBoss Tools</property> from one o=
f our update sites: <itemizedlist>
       <listitem>
        <para>Stable Updates: <ulink url=3D"http://download.jboss.org/jboss=
tools/updates/stable"
-        >http://download.jboss.org/jbosstools/updates/stable</ulink></para>
+         >http://download.jboss.org/jbosstools/updates/stable</ulink></par=
a>
       </listitem>
       <listitem>
        <para> Development Updates: <ulink


--===============2313568017653457278==--