]
Michelle Murray resolved TOOLSDOC-295.
--------------------------------------
Resolution: Done
Installation information is now contained in the Installation Guide.
The Java developer kit information has been rewritten and I believe the issue regarding
when to use the alternatives command is now resolved. As part of the system requirements,
the user is informed about compatible JDKs [1] and then stepped through how to check which
JDK their system uses and how to install another one if necessary. The alternatives
command is only introduced in the case that a user has to install a new JDK [2].
[1]
Tweaks to GSG section 3.1.1. Installing and Configuring 32-bit Sun
JDK 6 on Linux
---------------------------------------------------------------------------------
Key: TOOLSDOC-295
URL:
https://issues.jboss.org/browse/TOOLSDOC-295
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Getting Started Guide
Affects Versions: 4.0.0.Final
Reporter: Nick Boldt
Assignee: Michelle Murray
Fix For: 4.1.0
In GSG for JBDS 6 [1], section *3.1.1. Installing and Configuring 32-bit Sun JDK 6 on
Linux*, I see:
{quote}
You only need to run "alternative" as a safe guard for the right JVM.
{quote}
Suggest changing this to:
{quote}
You only need to run *alternatives* to select the correct default JDK.
{quote}
[1]
https://access.redhat.com/knowledge/docs/en-US/JBoss_Developer_Studio/6.0...
Note too that the JDK referenced is now called the Oracle JDK, not the Sun JDK.
{quote}
3.1.1. Installing and Configuring 32-bit *Sun* JDK 6 on Linux
To install 32-bit *Sun* JDK 6 on Linux and configure it, you should follow the next
steps:
Download the *Sun* JDK 6 from *Sun*'s website.
{quote}
--
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: