JBoss Tools SVN: r28383 - trunk/documentation/guides/GettingStartedGuide/en-US.
by jbosstools-commits@lists.jboss.org
Author: mcaspers
Date: 2011-01-18 21:32:01 -0500 (Tue, 18 Jan 2011)
New Revision: 28383
Modified:
trunk/documentation/guides/GettingStartedGuide/en-US/installation.xml
Log:
General Update
Modified: trunk/documentation/guides/GettingStartedGuide/en-US/installation.xml
===================================================================
--- trunk/documentation/guides/GettingStartedGuide/en-US/installation.xml 2011-01-19 02:16:57 UTC (rev 28382)
+++ trunk/documentation/guides/GettingStartedGuide/en-US/installation.xml 2011-01-19 02:32:01 UTC (rev 28383)
@@ -412,15 +412,15 @@
<listitem>
<para>Smooks Tools</para>
</listitem>
- <listitem>
+ <!--listitem>
<para>Deltacloud Tools</para>
- </listitem>
+ </listitem-->
</itemizedlist>
- <note>
+ <!--note>
<title>Note</title>
<para>The JBoss Tools Deltacloud component is not included with JBoss Developer Studio in this release.</para>
- </note>
+ </note-->
<para>To install the JBoss Tools plugins for Eclipse, you need the following:</para>
15 years, 2 months
JBoss Tools SVN: r28382 - trunk/documentation/guides/JBDS_Release_Notes/en-US.
by jbosstools-commits@lists.jboss.org
Author: mcaspers
Date: 2011-01-18 21:16:57 -0500 (Tue, 18 Jan 2011)
New Revision: 28382
Modified:
trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml
Log:
General Update
Modified: trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml
===================================================================
--- trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml 2011-01-19 02:07:09 UTC (rev 28381)
+++ trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml 2011-01-19 02:16:57 UTC (rev 28382)
@@ -25,7 +25,7 @@
<itemizedlist>
<listitem>
<para>
- <ulink url="https://issues.jboss.org/browse/JBIDE-7796">JBIDE-7796</ulink>: Previously the CDI Bean XML schemas were accessing them from the Internet by default. This could cause delays as the files are downloaded. Now the CDI Bean XML schemas are included in the <guilabel>XML Catalog</guilabel>. You can access the <guilabel>XML Catalog</guilabel> by selecting <menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Preferences</guimenuitem><guimenuitem>XML</guimenuitem><guimenuitem>XML Catalog</guimenuitem></menuchoice>.
+ <ulink url="https://issues.jboss.org/browse/JBIDE-7796">JBIDE-7796</ulink>: Previously the CDI Bean XML schemas were accessed from the Internet by default. This could cause delays as the files were downloaded. Now the CDI Bean XML schemas are included in the <guilabel>XML Catalog</guilabel>. You can access the <guilabel>XML Catalog</guilabel> by selecting <menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Preferences</guimenuitem><guimenuitem>XML</guimenuitem><guimenuitem>XML Catalog</guimenuitem></menuchoice>.
</para>
</listitem>
<listitem>
15 years, 2 months
JBoss Tools SVN: r28381 - trunk/documentation/guides/JBDS_Release_Notes/en-US.
by jbosstools-commits@lists.jboss.org
Author: mcaspers
Date: 2011-01-18 21:07:09 -0500 (Tue, 18 Jan 2011)
New Revision: 28381
Modified:
trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml
Log:
Added JBIDE-7796
Modified: trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml
===================================================================
--- trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml 2011-01-19 01:48:37 UTC (rev 28380)
+++ trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml 2011-01-19 02:07:09 UTC (rev 28381)
@@ -22,9 +22,14 @@
<formalpara>
<title>Contexts and Dependency Injection (CDI)</title>
<para>
- <itemizedlist>
+ <itemizedlist>
<listitem>
<para>
+ <ulink url="https://issues.jboss.org/browse/JBIDE-7796">JBIDE-7796</ulink>: Previously the CDI Bean XML schemas were accessing them from the Internet by default. This could cause delays as the files are downloaded. Now the CDI Bean XML schemas are included in the <guilabel>XML Catalog</guilabel>. You can access the <guilabel>XML Catalog</guilabel> by selecting <menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Preferences</guimenuitem><guimenuitem>XML</guimenuitem><guimenuitem>XML Catalog</guimenuitem></menuchoice>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
<ulink url="https://issues.jboss.org/browse/JBIDE-8124">JBIDE-8124</ulink>: The <guilabel>New CDI Bean</guilabel> wizard has been added to provide a convenient way to create new CDI Java classes with the <code>@Named</code>, <code>@Scope</code> and <code>@Qualifier</code> annotations. The wizard can be accessed by selecting <menuchoice><guimenuitem>File</guimenuitem><guimenuitem>New</guimenuitem><guimenuitem>Other</guimenuitem><guimenuitem>CDI (Context and Dependency Injection)</guimenuitem><guimenuitem>Bean</guimenuitem></menuchoice>.
</para>
</listitem>
15 years, 2 months
JBoss Tools SVN: r28380 - trunk/documentation/guides/JBDS_Release_Notes/en-US.
by jbosstools-commits@lists.jboss.org
Author: mcaspers
Date: 2011-01-18 20:48:37 -0500 (Tue, 18 Jan 2011)
New Revision: 28380
Modified:
trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml
Log:
General update
Modified: trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml
===================================================================
--- trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml 2011-01-19 01:47:28 UTC (rev 28379)
+++ trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml 2011-01-19 01:48:37 UTC (rev 28380)
@@ -25,7 +25,7 @@
<itemizedlist>
<listitem>
<para>
- <ulink url="https://issues.jboss.org/browse/JBIDE-8124">JBIDE-8124</ulink>: The <guilabel>New CDI Bean</guilabel> wizard has been added to provide a convenient way to create new CDI Java classes with the <code>@Named</code>, <scope>@Scope</scope> and <code>@Qualifier</code> annotations. The wizard can be accessed by selecting <menuchoice><guimenuitem>File</guimenuitem><guimenuitem>New</guimenuitem><guimenuitem>Other</guimenuitem><guimenuitem>CDI (Context and Dependency Injection)</guimenuitem><guimenuitem>Bean</guimenuitem></menuchoice>.
+ <ulink url="https://issues.jboss.org/browse/JBIDE-8124">JBIDE-8124</ulink>: The <guilabel>New CDI Bean</guilabel> wizard has been added to provide a convenient way to create new CDI Java classes with the <code>@Named</code>, <code>@Scope</code> and <code>@Qualifier</code> annotations. The wizard can be accessed by selecting <menuchoice><guimenuitem>File</guimenuitem><guimenuitem>New</guimenuitem><guimenuitem>Other</guimenuitem><guimenuitem>CDI (Context and Dependency Injection)</guimenuitem><guimenuitem>Bean</guimenuitem></menuchoice>.
</para>
</listitem>
<listitem>
15 years, 2 months
JBoss Tools SVN: r28379 - trunk/documentation/guides/JBDS_Release_Notes/en-US.
by jbosstools-commits@lists.jboss.org
Author: mcaspers
Date: 2011-01-18 20:47:28 -0500 (Tue, 18 Jan 2011)
New Revision: 28379
Modified:
trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml
Log:
Added JBIDE-8124
Modified: trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml
===================================================================
--- trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml 2011-01-19 01:01:29 UTC (rev 28378)
+++ trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml 2011-01-19 01:47:28 UTC (rev 28379)
@@ -23,6 +23,11 @@
<title>Contexts and Dependency Injection (CDI)</title>
<para>
<itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="https://issues.jboss.org/browse/JBIDE-8124">JBIDE-8124</ulink>: The <guilabel>New CDI Bean</guilabel> wizard has been added to provide a convenient way to create new CDI Java classes with the <code>@Named</code>, <scope>@Scope</scope> and <code>@Qualifier</code> annotations. The wizard can be accessed by selecting <menuchoice><guimenuitem>File</guimenuitem><guimenuitem>New</guimenuitem><guimenuitem>Other</guimenuitem><guimenuitem>CDI (Context and Dependency Injection)</guimenuitem><guimenuitem>Bean</guimenuitem></menuchoice>.
+ </para>
+ </listitem>
<listitem>
<para>
<ulink url="https://issues.jboss.org/browse/JBIDE-7875">JBIDE-7875</ulink>: It is recommended that developers create an Annotation Literal class for every qualifier in their public API. However, writing these classes by hand can be time consuming. To address this the new <guilabel>Annotation Literal Type</guilabel> wizard provides a streamlined way to create these classes. This wizard can be accessed by selecting <menuchoice>
15 years, 2 months
JBoss Tools SVN: r28378 - trunk/documentation/guides/JBDS_Release_Notes/en-US.
by jbosstools-commits@lists.jboss.org
Author: mcaspers
Date: 2011-01-18 20:01:29 -0500 (Tue, 18 Jan 2011)
New Revision: 28378
Modified:
trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml
Log:
General update
Modified: trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml
===================================================================
--- trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml 2011-01-19 00:55:17 UTC (rev 28377)
+++ trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml 2011-01-19 01:01:29 UTC (rev 28378)
@@ -336,7 +336,7 @@
<itemizedlist>
<listitem>
<para>
- <ulink url="https://issues.jboss.org/browse/JBIDE-7761">JBIDE-7761</ulink>: The <guimenuitem>Show in Remote System Explorer...</guimenuitem> option is now available in the Cloud View context menu.
+ <ulink url="https://issues.jboss.org/browse/JBIDE-7761">JBIDE-7761</ulink>: The <guimenuitem>Show in Remote System Explorer...</guimenuitem> option is now available in the <guilabel>Cloud Viewer<guilabel> context menu.
</para>
</listitem>
<listitem>
15 years, 2 months
JBoss Tools SVN: r28377 - trunk/documentation/guides/JBDS_Release_Notes/en-US.
by jbosstools-commits@lists.jboss.org
Author: mcaspers
Date: 2011-01-18 19:55:17 -0500 (Tue, 18 Jan 2011)
New Revision: 28377
Modified:
trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml
Log:
Added JBIDE-7761
Modified: trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml
===================================================================
--- trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml 2011-01-19 00:49:46 UTC (rev 28376)
+++ trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml 2011-01-19 00:55:17 UTC (rev 28377)
@@ -334,6 +334,11 @@
<title>Deltacloud</title>
<para>
<itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="https://issues.jboss.org/browse/JBIDE-7761">JBIDE-7761</ulink>: The <guimenuitem>Show in Remote System Explorer...</guimenuitem> option is now available in the Cloud View context menu.
+ </para>
+ </listitem>
<listitem>
<para>
<ulink url="https://issues.jboss.org/browse/JBIDE-7186">JBIDE-7186</ulink>: Previously when publishing to a remote server the progress bar and percentage indicator provided insufficient information on the actions that were being undertaken during what could be a time consuming process. In this version the progress monitor now shows more detailed information such as the name of the individual file that is being uploaded or the name of the directory that is currently being created.
15 years, 2 months
JBoss Tools SVN: r28376 - in workspace/rstryker/hudson/plugins: org.jboss.tools.hudson.manager.core/src/org/jboss/tools/hudson/manager/core/model and 3 other directories.
by jbosstools-commits@lists.jboss.org
Author: rob.stryker(a)jboss.com
Date: 2011-01-18 19:49:46 -0500 (Tue, 18 Jan 2011)
New Revision: 28376
Modified:
workspace/rstryker/hudson/plugins/org.jboss.tools.hudson.manager.core/META-INF/MANIFEST.MF
workspace/rstryker/hudson/plugins/org.jboss.tools.hudson.manager.core/src/org/jboss/tools/hudson/manager/core/model/HudsonJob.java
workspace/rstryker/hudson/plugins/org.jboss.tools.hudson.manager.core/src/org/jboss/tools/hudson/manager/core/model/HudsonModel.java
workspace/rstryker/hudson/plugins/org.jboss.tools.hudson.manager.core/src/org/jboss/tools/hudson/manager/core/util/HudsonXMLUtil.java
workspace/rstryker/hudson/plugins/org.jboss.tools.hudson.manager.ui/META-INF/MANIFEST.MF
workspace/rstryker/hudson/plugins/org.jboss.tools.hudson.manager.ui/src/org/jboss/tools/hudson/manager/ui/views/HudsonActionProvider.java
Log:
hudson tooling in workspace - checking in so nick can play
Modified: workspace/rstryker/hudson/plugins/org.jboss.tools.hudson.manager.core/META-INF/MANIFEST.MF
===================================================================
--- workspace/rstryker/hudson/plugins/org.jboss.tools.hudson.manager.core/META-INF/MANIFEST.MF 2011-01-19 00:36:28 UTC (rev 28375)
+++ workspace/rstryker/hudson/plugins/org.jboss.tools.hudson.manager.core/META-INF/MANIFEST.MF 2011-01-19 00:49:46 UTC (rev 28376)
@@ -9,7 +9,29 @@
org.eclipse.equinox.security;bundle-version="1.0.200"
Bundle-ActivationPolicy: lazy
Bundle-RequiredExecutionEnvironment: JavaSE-1.6
-Export-Package: org.jboss.tools.hudson.manager.core,
+Export-Package: org.apache.commons.httpclient,
+ org.apache.commons.httpclient.auth,
+ org.apache.commons.httpclient.cookie,
+ org.apache.commons.httpclient.methods,
+ org.apache.commons.httpclient.methods.multipart,
+ org.apache.commons.httpclient.params,
+ org.apache.commons.httpclient.protocol,
+ org.apache.commons.httpclient.util,
+ org.dom4j,
+ org.dom4j.bean,
+ org.dom4j.datatype,
+ org.dom4j.dom,
+ org.dom4j.dtd,
+ org.dom4j.io,
+ org.dom4j.jaxb,
+ org.dom4j.rule,
+ org.dom4j.rule.pattern,
+ org.dom4j.swing,
+ org.dom4j.tree,
+ org.dom4j.util,
+ org.dom4j.xpath,
+ org.dom4j.xpp,
+ org.jboss.tools.hudson.manager.core,
org.jboss.tools.hudson.manager.core.jobs,
org.jboss.tools.hudson.manager.core.model
Bundle-ClassPath: libs/commons-httpclient-3.1.jar,
Modified: workspace/rstryker/hudson/plugins/org.jboss.tools.hudson.manager.core/src/org/jboss/tools/hudson/manager/core/model/HudsonJob.java
===================================================================
--- workspace/rstryker/hudson/plugins/org.jboss.tools.hudson.manager.core/src/org/jboss/tools/hudson/manager/core/model/HudsonJob.java 2011-01-19 00:36:28 UTC (rev 28375)
+++ workspace/rstryker/hudson/plugins/org.jboss.tools.hudson.manager.core/src/org/jboss/tools/hudson/manager/core/model/HudsonJob.java 2011-01-19 00:49:46 UTC (rev 28376)
@@ -1,19 +1,20 @@
package org.jboss.tools.hudson.manager.core.model;
-import java.net.URL;
import java.util.ArrayList;
import java.util.Collections;
import java.util.Comparator;
import java.util.List;
+import org.apache.commons.httpclient.HttpClient;
+import org.apache.commons.httpclient.HttpMethod;
+import org.apache.commons.httpclient.methods.GetMethod;
import org.dom4j.Document;
-import org.dom4j.DocumentException;
-import org.dom4j.DocumentHelper;
import org.dom4j.Element;
import org.dom4j.Node;
import org.dom4j.io.SAXReader;
import org.eclipse.core.runtime.IPath;
import org.eclipse.core.runtime.Path;
+import org.jboss.tools.hudson.manager.core.util.HudsonXMLUtil;
public class HudsonJob {
private HudsonServer fserver;
@@ -25,9 +26,13 @@
this.furl = url;
this.fcolor = color;
}
- public static String getTrimJobUrl(HudsonServer server, String name) {
- return server.getTrimUrl() + "job" + Path.SEPARATOR + name + Path.SEPARATOR + HudsonModel.API_XML_DEPT_1;
+ public static String getTrimJobUrl(HudsonServer server, String jobName) {
+ return server.getTrimUrl() + "job" + Path.SEPARATOR + jobName + Path.SEPARATOR + HudsonModel.API_XML_DEPT_1;
}
+ public static String getConfigXMLUrl(HudsonServer server, String jobName) {
+ return server.getTrimUrl() + "job" + Path.SEPARATOR + jobName + Path.SEPARATOR + HudsonModel.CONFIG_XML;
+ }
+
public HudsonServer getServer() {
return fserver;
}
@@ -41,6 +46,23 @@
return fcolor;
}
+ public String fetchJobConfigXml() {
+ String url = getConfigXMLUrl(fserver, fname);
+ try {
+// String url = "http://hudson.qa.jboss.com/hudson/view/DevStudio_Trunk/job/jbosstools-3.2...";
+ HttpClient client = new HudsonXMLUtil().getHttpClient(
+ fserver.getTrimUrl(), fserver.getUser(), fserver.getPassword());
+ HttpMethod method = new GetMethod(url);
+ client.executeMethod(method);
+ if(method.getStatusCode() / 100 != 2 ) {
+ Document dom = new SAXReader().read(method.getResponseBodyAsStream());
+ return dom.asXML();
+ }
+ } catch(Exception e) {
+ }
+ return null;
+ }
+
public boolean detailsLoaded() {
return fdetails != null;
}
Modified: workspace/rstryker/hudson/plugins/org.jboss.tools.hudson.manager.core/src/org/jboss/tools/hudson/manager/core/model/HudsonModel.java
===================================================================
--- workspace/rstryker/hudson/plugins/org.jboss.tools.hudson.manager.core/src/org/jboss/tools/hudson/manager/core/model/HudsonModel.java 2011-01-19 00:36:28 UTC (rev 28375)
+++ workspace/rstryker/hudson/plugins/org.jboss.tools.hudson.manager.core/src/org/jboss/tools/hudson/manager/core/model/HudsonModel.java 2011-01-19 00:49:46 UTC (rev 28376)
@@ -25,6 +25,7 @@
public class HudsonModel {
public static final String API_XML = "api/xml";
public static final String API_XML_DEPT_1 = API_XML + "?depth=1";
+ public static final String CONFIG_XML = "config.xml";
private static HudsonModel instance = null;
public static HudsonModel getInstance() {
@@ -175,6 +176,7 @@
repo.put(url, document);
} catch(Exception e) {
// TODO log
+ e.printStackTrace();
}
}
}
Modified: workspace/rstryker/hudson/plugins/org.jboss.tools.hudson.manager.core/src/org/jboss/tools/hudson/manager/core/util/HudsonXMLUtil.java
===================================================================
--- workspace/rstryker/hudson/plugins/org.jboss.tools.hudson.manager.core/src/org/jboss/tools/hudson/manager/core/util/HudsonXMLUtil.java 2011-01-19 00:36:28 UTC (rev 28375)
+++ workspace/rstryker/hudson/plugins/org.jboss.tools.hudson.manager.core/src/org/jboss/tools/hudson/manager/core/util/HudsonXMLUtil.java 2011-01-19 00:49:46 UTC (rev 28376)
@@ -21,22 +21,20 @@
import org.dom4j.Document;
import org.dom4j.DocumentException;
import org.dom4j.io.SAXReader;
+import org.jboss.tools.hudson.manager.core.model.HudsonJob;
public class HudsonXMLUtil {
private boolean verbose = false;
- private String USERNAME = "admin";
- private String PASSWORD = "chestnuts";
- private String hudsonURL = "http://localhost:8080/";
// use like this to submit an updated config.xml to the server:
// postXML(configXMLFile, null, hudsonURL + "job/" + jobName +
// "/config.xml", true);
- private String[] postXML(String xmlFile, String xmlContents, String jobURL,
- boolean getErrorMessage) {
- return postXML(new File(xmlFile), xmlContents, jobURL, getErrorMessage);
- }
+// private String[] postXML(String xmlFile, String xmlContents, String jobURL,
+// boolean getErrorMessage) {
+// return postXML(new File(xmlFile), xmlContents, jobURL, getErrorMessage);
+// }
/**
*
@@ -46,11 +44,12 @@
* @param getErrorMessage - return a string[] containing result code, or code + message
* @return
*/
- private String[] postXML(File xmlFile, String xmlContents, String jobURL,
+ private String[] postXML(HudsonJob job,
+ File xmlFile, String xmlContents,
boolean getErrorMessage) {
int resultCode = -1;
String responseBody = "";
- PostMethod post = new PostMethod(jobURL);
+ PostMethod post = new PostMethod(job.getUrl());
HttpClient client = null;
if (xmlFile == null && xmlContents != null) {
@@ -91,7 +90,8 @@
post.setRequestHeader("Content-type", "text/xml; charset=ISO-8859-1");
if (client == null) {
- client = getHttpClient(USERNAME, PASSWORD);
+ client = getHttpClient(job.getServer().getUrl(),
+ job.getServer().getUser(), job.getServer().getPassword());
}
try {
resultCode = client.executeMethod(post);
@@ -172,13 +172,13 @@
return out;
}
- public HttpClient getHttpClient(String username, String password) {
+ public HttpClient getHttpClient(String rootUrl, String username, String password) {
HttpClient client = new HttpClient();
// establish a connection within 5 seconds
client.getHttpConnectionManager().getParams()
.setConnectionTimeout(5000);
- if (hudsonURL.indexOf("localhost") >= 0) {
+ if (rootUrl.indexOf("localhost") >= 0) {
/* simpler authentication method, may not work w/ secured Hudson */
Credentials creds = new UsernamePasswordCredentials(username,
password);
@@ -186,7 +186,7 @@
client.getState().setCredentials(AuthScope.ANY, creds);
}
} else {
- GetMethod login = new GetMethod(hudsonURL + "loginEntry");
+ GetMethod login = new GetMethod(rootUrl + "loginEntry");
try {
client.executeMethod(login);
} catch (HttpException e) {
@@ -200,7 +200,7 @@
e.printStackTrace();
}
- String location = hudsonURL + "j_security_check";
+ String location = rootUrl + "j_security_check";
while (true) {
PostMethod loginMethod = new PostMethod(location);
loginMethod.addParameter("j_username", username);
@@ -232,7 +232,7 @@
return client;
}
- private static void checkResult(int i, URI uri) throws IOException {
+ public static void checkResult(int i, URI uri) throws IOException {
if (i / 100 != 2) {
// System.out.println("[WARN] Got result: " + i + " for "+
// uri.toString());
Modified: workspace/rstryker/hudson/plugins/org.jboss.tools.hudson.manager.ui/META-INF/MANIFEST.MF
===================================================================
--- workspace/rstryker/hudson/plugins/org.jboss.tools.hudson.manager.ui/META-INF/MANIFEST.MF 2011-01-19 00:36:28 UTC (rev 28375)
+++ workspace/rstryker/hudson/plugins/org.jboss.tools.hudson.manager.ui/META-INF/MANIFEST.MF 2011-01-19 00:49:46 UTC (rev 28376)
@@ -20,3 +20,17 @@
org.jboss.tools.hudson.manager.core;bundle-version="1.0.0"
Bundle-ActivationPolicy: lazy
Bundle-RequiredExecutionEnvironment: JavaSE-1.6
+Import-Package: org.dom4j,
+ org.dom4j.bean,
+ org.dom4j.datatype,
+ org.dom4j.dom,
+ org.dom4j.dtd,
+ org.dom4j.io,
+ org.dom4j.jaxb,
+ org.dom4j.rule,
+ org.dom4j.rule.pattern,
+ org.dom4j.swing,
+ org.dom4j.tree,
+ org.dom4j.util,
+ org.dom4j.xpath,
+ org.dom4j.xpp
Modified: workspace/rstryker/hudson/plugins/org.jboss.tools.hudson.manager.ui/src/org/jboss/tools/hudson/manager/ui/views/HudsonActionProvider.java
===================================================================
--- workspace/rstryker/hudson/plugins/org.jboss.tools.hudson.manager.ui/src/org/jboss/tools/hudson/manager/ui/views/HudsonActionProvider.java 2011-01-19 00:36:28 UTC (rev 28375)
+++ workspace/rstryker/hudson/plugins/org.jboss.tools.hudson.manager.ui/src/org/jboss/tools/hudson/manager/ui/views/HudsonActionProvider.java 2011-01-19 00:49:46 UTC (rev 28376)
@@ -1,5 +1,6 @@
package org.jboss.tools.hudson.manager.ui.views;
+import org.dom4j.Document;
import org.eclipse.jface.action.Action;
import org.eclipse.jface.action.IMenuManager;
import org.eclipse.jface.action.Separator;
@@ -14,7 +15,9 @@
public class HudsonActionProvider extends AbstractCommonNavActionProvider {
private Action newConnectionAction, deleteConnectionAction,
- refreshJobAction, openBuiltOnAction;
+ refreshJobAction, openBuiltOnAction,
+ printConfigXml;
+
public HudsonActionProvider() {
super();
}
@@ -31,8 +34,10 @@
menu.add(visible);
if (first == null)
return;
- if( getSelectedItem() instanceof HudsonJob )
+ if( getSelectedItem() instanceof HudsonJob ) {
menu.add(refreshJobAction);
+ menu.add(this.printConfigXml);
+ }
if( getSelectedItem() instanceof JobBuild) {
menu.add(openBuiltOnAction);
String builtOn = ((JobBuild)getSelectedItem()).getBuiltOn();
@@ -80,6 +85,17 @@
}
};
openBuiltOnAction.setText("Open Build Machine");
+ printConfigXml = new Action() {
+ public void run() {
+ tempAction();
+ }
+ };
+ printConfigXml.setText("Print Config.xml");
+
}
//http://hudson.qa.jboss.com/hudson/computer/dev90-linux/
+ public void tempAction() {
+ HudsonJob j = ((HudsonJob)getSelectedItem());
+ System.out.println(j.fetchJobConfigXml());
+ }
}
15 years, 2 months
JBoss Tools SVN: r28375 - trunk/documentation/guides/GettingStartedGuide/en-US.
by jbosstools-commits@lists.jboss.org
Author: mcaspers
Date: 2011-01-18 19:36:28 -0500 (Tue, 18 Jan 2011)
New Revision: 28375
Added:
trunk/documentation/guides/GettingStartedGuide/en-US/.directory
trunk/documentation/guides/GettingStartedGuide/en-US/Installation_Guide.ent
trunk/documentation/guides/GettingStartedGuide/en-US/Installation_Guide.xml
trunk/documentation/guides/GettingStartedGuide/en-US/Installation_Revision_History.xml
trunk/documentation/guides/GettingStartedGuide/en-US/installation.xml
trunk/documentation/guides/GettingStartedGuide/en-US/introduction.xml
Modified:
trunk/documentation/guides/GettingStartedGuide/en-US/Book_Info.xml
trunk/documentation/guides/GettingStartedGuide/en-US/Getting_Started_Guide.xml
trunk/documentation/guides/GettingStartedGuide/en-US/getting_started.xml
Log:
Split chapters and created Installation Guide
Added: trunk/documentation/guides/GettingStartedGuide/en-US/.directory
===================================================================
--- trunk/documentation/guides/GettingStartedGuide/en-US/.directory (rev 0)
+++ trunk/documentation/guides/GettingStartedGuide/en-US/.directory 2011-01-19 00:36:28 UTC (rev 28375)
@@ -0,0 +1,5 @@
+[Dolphin]
+AdditionalInfo=35
+Sorting=6
+Timestamp=2011,1,19,9,32,36
+ViewMode=1
Modified: trunk/documentation/guides/GettingStartedGuide/en-US/Book_Info.xml
===================================================================
--- trunk/documentation/guides/GettingStartedGuide/en-US/Book_Info.xml 2011-01-19 00:17:47 UTC (rev 28374)
+++ trunk/documentation/guides/GettingStartedGuide/en-US/Book_Info.xml 2011-01-19 00:36:28 UTC (rev 28375)
@@ -21,3 +21,26 @@
<xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
<xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
</bookinfo>
+
+<!-- The following code is used to build an installation guide, which includes only the installation.xml file. To build the Installation Guide simply uncomment the following <bookinfo> tag and comment out the <bookinfo> tag above -->
+
+<!--bookinfo>
+ <title>Installation Guide</title>
+ <subtitle>Provides information on how to install JBoss Developer Studio.</subtitle>
+ <productname>JBoss Developer Studio</productname>
+ <productnumber>4.0</productnumber>
+ <edition>4.0.0</edition>
+ <pubsnumber>1</pubsnumber>
+ <abstract>
+ <para>JBoss Developer Studio Installation Guide.</para>
+ </abstract>
+ <corpauthor>
+ <inlinemediaobject>
+ <imageobject>
+ <imagedata fileref="Common_Content/images/title_logo.svg" format="SVG"></imagedata>
+ </imageobject>
+ </inlinemediaobject>
+ </corpauthor>
+ <xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+ <xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+</bookinfo-->
Modified: trunk/documentation/guides/GettingStartedGuide/en-US/Getting_Started_Guide.xml
===================================================================
--- trunk/documentation/guides/GettingStartedGuide/en-US/Getting_Started_Guide.xml 2011-01-19 00:17:47 UTC (rev 28374)
+++ trunk/documentation/guides/GettingStartedGuide/en-US/Getting_Started_Guide.xml 2011-01-19 00:36:28 UTC (rev 28375)
@@ -4,6 +4,8 @@
<book>
<xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
<xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
<xi:include href="getting_started.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
<xi:include href="manage.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
<xi:include href="first_seam.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
Added: trunk/documentation/guides/GettingStartedGuide/en-US/Installation_Guide.ent
===================================================================
--- trunk/documentation/guides/GettingStartedGuide/en-US/Installation_Guide.ent (rev 0)
+++ trunk/documentation/guides/GettingStartedGuide/en-US/Installation_Guide.ent 2011-01-19 00:36:28 UTC (rev 28375)
@@ -0,0 +1,4 @@
+<!ENTITY PRODUCT "JBoss">
+<!ENTITY BOOKID "Installation_Guide">
+<!ENTITY YEAR "2011">
+<!ENTITY HOLDER "Red Hat">
Added: trunk/documentation/guides/GettingStartedGuide/en-US/Installation_Guide.xml
===================================================================
--- trunk/documentation/guides/GettingStartedGuide/en-US/Installation_Guide.xml (rev 0)
+++ trunk/documentation/guides/GettingStartedGuide/en-US/Installation_Guide.xml 2011-01-19 00:36:28 UTC (rev 28375)
@@ -0,0 +1,9 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<book>
+<xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<xi:include href="Installation_Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+</book>
Added: trunk/documentation/guides/GettingStartedGuide/en-US/Installation_Revision_History.xml
===================================================================
--- trunk/documentation/guides/GettingStartedGuide/en-US/Installation_Revision_History.xml (rev 0)
+++ trunk/documentation/guides/GettingStartedGuide/en-US/Installation_Revision_History.xml 2011-01-19 00:36:28 UTC (rev 28375)
@@ -0,0 +1,24 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+<appendix>
+ <title>Revision History</title>
+ <simpara>
+ <revhistory>
+ <revision>
+ <revnumber>0</revnumber>
+ <date>Wed Jan 19 2011</date>
+ <author>
+ <firstname>Matthew</firstname>
+ <surname>Casperson</surname>
+ <email>mcaspers(a)redhat.com</email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Initial creation of book</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+ </revhistory>
+ </simpara>
+</appendix>
Modified: trunk/documentation/guides/GettingStartedGuide/en-US/getting_started.xml
===================================================================
--- trunk/documentation/guides/GettingStartedGuide/en-US/getting_started.xml 2011-01-19 00:17:47 UTC (rev 28374)
+++ trunk/documentation/guides/GettingStartedGuide/en-US/getting_started.xml 2011-01-19 00:36:28 UTC (rev 28375)
@@ -1,1041 +1,296 @@
<?xml version="1.0" encoding="UTF-8"?>
<chapter id="getting_started">
- <?dbhtml filename="getting_started.html"?>
- <chapterinfo>
- <keywordset>
- <keyword>JBoss Developer Studio</keyword>
- <keyword>Eclipse</keyword>
- <keyword>Java</keyword>
- <keyword>JBoss</keyword>
- </keywordset>
- </chapterinfo>
- <title>Getting Started with JBoss Developer Studio</title>
+ <?dbhtml filename="getting_started.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>Getting Started with JBoss Developer Studio</title>
- <section id="intro1">
- <title>What is JBDS?</title>
- <para><property>JBoss Developer Studio</property> is a set of eclipse-based development tools that
- have been pre-configured for JBoss Enterprise Middleware Platforms and Red Hat Enterprise Linux.
- Developers are not required to use <property>JBoss Developer Studio</property> to develop on
- JBoss Enterprise Middleware and/or Red Hat Linux. But, many find these pre-configured tools offer
- significant time-savings and value, making them more pra JSPoductive reducing deployment times.</para>
- <para>This guide covers the first steps required to get started with <property>JBoss Developer
- Studio</property>. You will learn how to install and configure the software necessary for your OS
- (currently Linux, Microsoft Windows or Mac OSX), including detailed information on how to install, configure and use JDK, JBDS and JBoss
- Tools.</para>
- </section>
+ <section id="Welcome">
+ <title>Welcome to JBoss Developer Studio</title>
+ <para>In this section we'll show you how to work with the welcome page of the <property>JBoss Developer Studio</property>.</para>
+ <para>The welcome page is the first page you see when you first launch <property>JBoss Developer Studio</property>. </para>
-<section>
- <title>Key Features of JBoss Developer Studio and Requirements</title>
- <para>The table below lists the main features of JBoss Developer Studio:</para>
+ <figure>
+ <title>Welcome to JBoss Developer Studio</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/getting_started/getting_started_5.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
- <table>
-
- <title>Key Functionality of JBoss Developer Studio</title>
- <tgroup cols="2">
-
- <colspec colnum="1" align="left" colwidth="2*"/>
- <colspec colnum="2" colwidth="4*"/>
-
-
- <thead>
- <row>
- <entry>Feature</entry>
- <entry>Benefit</entry>
-
- </row>
- </thead>
-
- <tbody>
-
- <row>
- <entry><para>JBoss Enterprise Application Platform</para></entry>
- <entry><para>JBoss Developer Studio includes and integrates JBoss Enterprise Application Platform, the same version of the middleware platform that Red Hat supports in production for 5 years.</para></entry>
- </row>
-
- <row>
- <entry><para>New Seam Tools</para></entry>
- <entry><para>JBoss Developer Studio includes brand new tools for Seam. They provide wizards for creating new Seam projects, validation tools, expression language code completion, testing tools, and wizards for generating entity objects.</para></entry>
- </row>
-
- <row>
- <entry><para>Visual Page Editor</para></entry>
- <entry><para>JBoss Developer Studio includes a Visual Page Editor for combined visual and source editing of Web pages. The Visual Page Editor even renders AJAX-enabled RichFaces components.</para></entry>
- </row>
-
- <row>
- <entry><para>AJAX Capabilities</para></entry>
- <entry><para>JBoss Developer Studio includes a Technology Preview of JBoss RichFaces. RichFaces provides nearly 70 skinnable components, including calendar, tree, dropdown menu, drag-and-drop components, and more. JBoss Developer Studio’s Visual Page Editor can render RichFaces components.</para></entry>
- </row>
-
- <row>
- <entry><para>JBoss Tools Palette</para></entry>
- <entry><para>The JBoss Tools Palette contains a developer’s project tag libraries and enables inserting tags into a JSP file with one click. The Tools Palette supports custom and 3rd party tags.</para></entry>
- </row>
-
- <row>
- <entry><para>JBoss jBPM Tools</para></entry>
- <entry><para>JBoss Developer Studio includes jBPM tooling for defining Seam page flows.</para></entry>
- </row>
-
- <row>
- <entry><para>Spring Tools</para></entry>
- <entry><para>JBoss Developer Studio includes Spring IDE for developing Spring applications.</para></entry>
- </row>
-
- <row>
- <entry><para>Struts Tools</para></entry>
- <entry><para>JBoss Developer Studio includes Struts tools for Struts 1.x applications.</para></entry>
- </row>
-
- <row>
- <entry><para>Optimized JBoss Application Server adapter</para></entry>
- <entry><para>JBoss Developer Studio’s advanced JBoss AS adapter includes features like incremental deployment for fast development and is pre-configured for the included JBoss Application server.</para></entry>
- </row>
-
- <row>
- <entry><para>Red Hat Enterprise Linux and RHN Access</para></entry>
- <entry><para>JBoss Developer Studio includes access to Red Hat Enterprise Linux, Linux development tools, and Red Hat Network for development purposes.</para></entry>
- </row>
-
- <row>
- <entry><para> Project Examples</para></entry>
- <entry><para> Tooling for easy installation of Examples.</para></entry>
- </row>
-
- <row>
- <entry><para>JBossWeb Service</para></entry>
- <entry><para>JBoss WS is a web service framework developed as a part of the JBoss Application Server. It implements the JAX-WS specification that defines a programming model and run-time architecture for implementing web services in Java, targeted at the Java Platform, Enterprise Edition 5 (Java EE 5).</para></entry>
- </row>
-
- <row>
- <entry><para>Usage reporting</para></entry>
- <entry><para>The usage plug-in anonymously gathers information on how you use the provided tools. This information is used to improve and shape the JBoss Developer Studio product to better cater to your needs. For more information refer to <xref linkend="Usage_Reporting"/>.</para></entry>
- </row>
- </tbody>
- </tgroup>
- </table>
-
- <para><property>JBDS</property> requires JDK 5+ (JDK 6 in case of EAP 5.0). Also it's important that
- the JVM's architecture matches the particular <property>JBDS</property> build, i.e. if you're on a
- 64-bit system and use the 64-bit JVM, you need the 64-bit JBDS.</para>
-
- <para>For the 32-bit version of JBDS use the 32-bit JVM or just use <literal>-vm</literal> flag to
- tell JBDS to use 32-bit java if the 64-bit one is found as the default.</para>
-
- <note>
- <title>Note:</title>
- <para>On Linux system with 64-bit JVM the visual editor may fail to start. In this case you need the <literal>libstdc++.so.5</literal> library.
- See also the <link linkend="question_1">FAQ</link>.</para>
- </note>
-</section>
-
- <section id="ConfigJavaEnvironment">
- <?dbhtml filename="ConfigJavaEnvironment.html"?>
- <title>Configuring Your Java Environment</title>
- <para>You must have a working installation of JDK before you install <property>JBoss Developer
- Studio</property>. Thus in this
- guide we will show you how to install a 32-bit Sun JDK 5.0 on a Linux Platform and Microsoft
- Windows Platform.</para>
+ <para>With the help of its page you will be able:</para>
+ <itemizedlist>
+ <listitem>
+ <para>to get quick access to Getting Started Documentation (guides, tutorials and viewlets)</para>
+ </listitem>
+ </itemizedlist>
- <section id="InstallJDK50onLinux">
- <title>Installing and Configuring 32-bit Sun JDK 5.0 on Linux</title>
- <para>To install 32-bit Sun JDK 5.0 on Linux and configure it, you should follow the next steps:</para>
- <itemizedlist>
- <listitem>
- <para>Download the <ulink url="http://java.sun.com/javase/downloads/index_jdk5.jsp">Sun JDK 5.0
- (Java 2 Development Kit)</ulink> from Sun's website. Choose "JDK 5.0 Update
- <x>" (where "x" is the latest update number) for
- download and then select "Red Hat Package Manager in self-extracting" file
- for Linux. Read the instructions on Sun's website for installing the JDK.</para>
- </listitem>
- <listitem>
- <para>If you don't want to use SysV service scripts you can install the
- "self-extracting file" for Linux instead of choosing the "RPM in
- self-extracting" file. In that case you can skip the next step mentioned here. But it
- is recommended to use the SysV service scripts for production servers.</para>
- </listitem>
- <listitem>
- <para>Download and install the appropriate -compat RPM from JPackage <ulink url="ftp://jpackage.hmdc.harvard.edu/JPackage/1.7/generic/RPMS.non-free/">here</ulink>.
- Please ensure you choose a matching version of the -compat package to the JDK you've
- installed.</para>
- </listitem>
- <listitem>
- <para>Create an environment variable that points to the JDK installation directory and call it
- JAVA_HOME. Add <emphasis>
- <property>$JAVA_HOME/bin</property>
- </emphasis> to the system path to be able to run java from the command line. You can do this
- by adding the following lines to the .bashrc file in your home directory.</para>
- <programlisting><![CDATA[#In this example /usr/java/jdk1.5.0_11 is the JDK installation directory.
-export JAVA_HOME=/usr/java/jdk1.5.0_11
-export PATH=$PATH:$JAVA_HOME/bin]]></programlisting>
- </listitem>
- </itemizedlist>
+ <figure>
+ <title>Getting Started Documentation</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/getting_started/getting_started_6.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
- <note>
- <title>Note:</title>
+ <itemizedlist>
+ <listitem>
+ <para>to create new Seam projects, jBPM Process, JSF or Struts projects using JBDS wizards</para>
+ </listitem>
+ </itemizedlist>
- <para>If you have JDK already installed and added in your system path, you should add
- <emphasis>$JAVA_HOME/bin</emphasis> before the old <emphasis>$PATH</emphasis> (not after it)
- so that the new version of JDK can be found first, i. e. <emphasis>
- <emphasis>export PATH=$JAVA_HOME/bin:$PATH</emphasis>
- </emphasis> This way, the machine will pick up the new JVM first. You only need to run
- "alternative" as a safe guard for the right JVM. </para>
- </note>
+ <figure>
+ <title>Create New...</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/getting_started/getting_started_7.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
- <para>Set this variable for your account doing the installation and also for the user account
- that will run the server.</para>
- <itemizedlist>
- <listitem>
- <para>If you have more than one version of JVM installed on your machine, make sure you are
- using the JDK 1.5 installation as the default java and javac. You can do this using the
- alternatives system. The alternatives system allows different versions of Java from different
- sources to co-exist on your system.</para>
- </listitem>
- </itemizedlist>
- <section id="SelectAlternativesforJava">
- <title>Select alternatives for java, javac and java_sdk_1.5.0</title>
- <itemizedlist>
- <listitem>
- <para>As a root user, type the following command at the shell prompt and you should see
- something like this:</para>
- </listitem>
- </itemizedlist>
- <programlisting><![CDATA[[root@vsr ~]$ /usr/sbin/alternatives --config java
-There are 2 programs that provide 'java'.
-Selection Command
------------------------------------------------
- 1 /usr/lib/jvm/jre-1.4.2-gcj/bin/java
-*+ 2 /usr/lib/jvm/jre-1.5.0-sun/bin/java
-Enter to keep the current selection[+], or type selection number:]]></programlisting>
- <para>Make sure the Sun version [jre-1.5.0-sun in this case] is selected (marked with a
- '+' in the output), or select it by entering its number as prompted.</para>
- <itemizedlist>
- <listitem>
- <para>Repeat the same for javac and java_sdk_1.5.0.</para>
- </listitem>
- </itemizedlist>
- <programlisting><![CDATA[[root@vsr ~]$ /usr/sbin/alternatives --config javac
-There is 1 program that provides 'javac'.
- Selection Command
------------------------------------------------
-*+ 1 /usr/lib/jvm/java-1.5.0-sun/bin/javac
-Enter to keep the current selection[+], or type selection number:
+ <itemizedlist>
+ <listitem>
+ <para>to get short descriptions of the perspectives that JBDS provides</para>
+ </listitem>
+ </itemizedlist>
-[root@vsr ~]$ /usr/sbin/alternatives --config java_sdk_1.5.0
-There is 1 program that provide 'java_sdk_1.5.0'.
- Selection Command
------------------------------------------------
-*+ 1 /usr/lib/jvm/java-1.5.0-sun
-Enter to keep the current selection[+], or type selection number:]]></programlisting>
- <para>You should verify that java, javac and java_sdk_1.5.0 all point to the same manufacturer
- and version.</para>
- <note>
- <title>Note:</title>
- <para>You can always override this step by setting the JAVA_HOME environment variable as
- explained in the previous step.</para>
- </note>
- <itemizedlist>
- <listitem>
- <para>Make sure that the java executable is in your path and that you are using an appropriate
- version. To verify your Java environment, type "java -version" at the shell
- prompt and you should see something like this:</para>
- </listitem>
- </itemizedlist>
- <programlisting><![CDATA[[root@vsr ~]$ java -version
-java version "1.5.0_11"
-Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
-Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode, sharing)]]></programlisting>
- </section>
+ <figure>
+ <title>Perspectives</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/getting_started/getting_started_8.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
- </section>
- <section id="InstallJDK50onWindows">
- <title>Installing and Configuring 32-bit Sun JDK 5.0 on Microsoft Windows</title>
+ <itemizedlist>
+ <listitem>
+ <para>to visit JBoss Developer Studio web resources.</para>
+ </listitem>
+ </itemizedlist>
- <para>To install and configure 32-bit Sun JDK 5.0 on Microsoft Windows, follow these steps:</para>
- <itemizedlist>
- <listitem>
- <para>Download the <ulink url="http://java.sun.com/javase/downloads/index_jdk5.jsp">Sun JDK 5.0
- (Java 2 Development Kit)</ulink> from Sun's website. Choose "JDK 5.0 Update
- <x>" (where "x" is the latest update number) for
- download and then select your Windows Platform options to perform the installation.</para>
- </listitem>
- <listitem>
- <para>Create an environment variable called JAVA_HOME that points to the JDK installation
- directory, for example:
- <emphasis>C:\Program Files\Java\jdk1.5.0_11\</emphasis>
- </para>
- </listitem>
- </itemizedlist>
+ <figure>
+ <title>Web Resources</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/getting_started/getting_started_9.png" scale="90"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
- <para>In order to run java from the command line, add the <emphasis>jre\bin</emphasis> directory
- to your path, for example:</para>
- <para>
- <emphasis>C:\Program Files\Java\jdk1.5.0_11\jre\bin</emphasis>
- </para>
- <para>To do this, open the <emphasis>
- <property>Control Panel</property>
- </emphasis> from the <emphasis>
- <property>Start</property>
- </emphasis> menu, switch to Classic View if necessary, open the System Control Panel applet (<emphasis>
- <property>System</property>
- </emphasis>), select the <emphasis>
- <property>Advanced</property>
- </emphasis> Tab, and click on the <emphasis>
- <property>Environment Variables</property>
- </emphasis> button.</para>
- <para>Now, when 32-bit Sun JDK 5.0 has been successfully installed, we can pass on to the next
- step.</para>
- </section>
+ <para>
+ You can start working with <property>JBoss Developer Studio</property> by clicking on <emphasis><property>Workbench</property></emphasis> button or simply closing the Welcome page.
+ </para>
- </section>
+ </section>
- <section id="InstallingJBDS">
- <?dbhtml filename="InstallingRHDS.html"?>
- <title>JBoss Developer Studio Installation</title>
+ <section id="Upgrading">
+ <?dbhtml filename="Upgrading.html"?>
+ <title>Upgrading</title>
+ <para>Because JBDS 3.0x and 4.0 use different versions of Eclipse, it is not possible to directly upgrade from an older version to JBDS 4.0.</para>
+ <note>
+ <title>Tip</title>
+ <para>It is possible to run JBDS 3.0x and 4.0 side by side, as long as they have been installed into separate directories.</para>
+ </note>
- <para>This chapter will provide you with detailed information on how to install <property>JBoss
- Developer Studio</property>.</para>
+ </section>
- <para>JBDS comes with a simple installer, bundled with tested and pre-configured versions of Eclipse,
- WTP, JBossEAP, Seam, and SpringIDE. The following steps show you how to install JBDS:</para>
+ <section id="Uninstalling">
+ <?dbhtml filename="Uninstalling.html"?>
+ <title>Uninstalling</title>
+ <itemizedlist>
+ <listitem>
+ <para>Make sure <property>JBoss Developer Studio</property> is not running</para>
+ </listitem>
+ <listitem>
+ <para>Uninstall your current version of <property>JBoss Developer Studio</property> by running the Uninstaller</para>
+ </listitem>
+ </itemizedlist>
+ </section>
- <itemizedlist>
- <listitem>
- <para>First of all you need the appropriate installation file for your platform from
- <ulink url="https://www.redhat.com/apps/store/developers/jboss_developer_studio.html">Red Hat
- website</ulink>.</para>
- </listitem>
- <listitem>
- <para>Run the following command in a terminal window:</para>
- <programlisting role="JAVA"><![CDATA[java -jar jbdevstudio-eap-linux-gtk-4.0.0.GA.jar
-]]></programlisting>
- </listitem>
- <listitem>
- <para>Follow the instructions presented by the installation wizard:</para>
- </listitem>
- </itemizedlist>
-
- <figure>
- <title>JBoss Developer Studio Installation Wizard</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/getting_started/getting_started_1.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <itemizedlist>
- <listitem>
- <para>Provide the installation path</para>
- </listitem>
- <listitem>
- <para>Select the appropriate Java Virtual Machine</para>
- </listitem>
- </itemizedlist>
-
- <note>
- <title>Tip:</title>
- <para>By selecting <emphasis>
- <property>Default Java VM</property>
- </emphasis> you set default Java VM of your system (to verify your Java environment, type
- "java -version" in console).</para>
- </note>
-
- <para>Selecting <emphasis>
- <property>Specific Java VM</property>
- </emphasis> you can provide the path to non-default Java VM.</para>
-
- <note>
- <title>Note:</title>
- <para>JBoss Developer Studio 4.0 comes integrated with JBoss EAP 5.1 that requires JDK 6.0 to run
- and "gij" isn't available on every platform.</para>
- </note>
-
- <figure>
- <title>Select Java VM</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/getting_started/getting_started_2.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <itemizedlist>
- <listitem>
- <para>As part of the installation you can choose to install <ulink url="http://www.jboss.com/products/platforms/application">JBoss Enterprise Application
- Platform</ulink>. Select <emphasis>
- <property>Yes</property></emphasis> to use it in JBoss Developer Studio.</para>
- <note>
- <title>Note:</title>
- <para>Like in the previous version of JBDS, JBDS 4.0.0.GA comes integrated with JBoss EAP 5.1 that supports EAP 5 adapter and Seam 2.2.</para>
- </note>
-
- <para>This step lets you configure locally available JBoss Application Servers: </para>
- </listitem>
- </itemizedlist>
-
- <figure>
- <title>JBoss Enterprise Application Platform Installing</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/getting_started/getting_started_3.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
-<itemizedlist>
- <listitem><para>You can fill the list automatically using the <guibutton>Find</guibutton> button. When the <guibutton>Find</guibutton> button is clicked you are propmpted to select the folder from which to search for available JBoss Application Servers. Click the <guibutton>OK</guibutton> button to select the chosen folder. </para> </listitem>
-</itemizedlist>
-
- <figure>
- <title>Finding Servers in the Selected Directory</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/getting_started/getting_started_3_3_1.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para/>
-
- <itemizedlist>
- <listitem><para> All available servers in the selected directory will be added to the list with the following details: Name, Type, Version and Location.
- </para></listitem>
- </itemizedlist>
-
- <itemizedlist>
- <listitem><para>You can also add servers one by one using the <guibutton>Add</guibutton> button:</para>
- </listitem>
- </itemizedlist>
-
- <figure>
- <title>Add Server to be Configured</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/getting_started/getting_started_3_1.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para/>
-
-<para>Click on the <guibutton>Browse</guibutton> button and select the server location. Fields Name, Type and Version will be filled in automatically:</para>
-
- <figure>
- <title>Specify Server Location</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/getting_started/getting_started_3_2.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para/>
-
-
- <para>When you click the <guibutton>OK</guibutton> button the server will be added to the list with the details on its type, version and location.</para>
-
- <para>The <guibutton>Remove</guibutton> button will the remove the selected server from the list. If necessary, you can edit the server details clicking on the <guibutton>Edit</guibutton> button:</para>
-
- <figure>
- <title>Edit Server</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/getting_started/getting_started_3_4.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para/>
-
- <!-- <note>
- <title>Note:</title>
- <para>The installer installs JBoss Enterprise Application Platform for running your applications
- if you select this option during the installation process. If you want to use a different server
- than ours, you can change the setting in JBoss Developer Studio.</para>
- </note>-->
-
- <itemizedlist>
- <listitem>
- <para>Click the <guibutton>Next</guibutton> button to bring up a summary page where you can check your installation paths and see the components that will be installed. If you'd like to change something, press the <guibutton>Previous</guibutton> button. Click the <guibutton>Next</guibutton> button to start installation. </para>
- </listitem>
- </itemizedlist>
-
- <para/>
-
- <figure>
- <title>Summary Information</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/getting_started/getting_started_4.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- </section>
-
- <section id="jbds_jbosstools">
-
- <title>JBoss Developer Studio and JBoss Tools</title>
-
- <para>This section highlights the differences between <property>JBoss Developer
- Studio</property> and <property>JBoss Tools</property>, and provides the steps on the <property>JBoss
- Tools</property> installation process.</para>
-
- <section id="WhatDifferenceBetweenJBDSAndJBossTools">
- <title>What is the difference?</title>
-
- <para><property>JBoss Tools</property> is a component of <property>JBoss Developer
- Studio</property>, which is designed to be an easy-to-install Eclipse based IDE, fully configured and ready
- to run with the bundled <property>JBoss Enterprise Application Platform</property>.</para>
-
- <para>In short <property>JBoss Tools</property> are just a set of Eclipse plugins and
- <property>JBoss Developer Studio</property> adds:</para>
- <itemizedlist>
- <listitem>
- <para>An installer</para>
- </listitem>
- <listitem>
- <para>Eclipse and Web Tools preconfigured</para>
- </listitem>
- <listitem>
- <para>JBoss EAP with JBoss AS and Seam preconfigured</para>
- </listitem>
- <listitem>
- <para>3rd party plugins bundled and configured</para>
- </listitem>
- <listitem>
- <para>Access to RHEL and Red Hat Network</para>
- </listitem>
- <listitem>
- <para>Access to the JBoss/Red Hat supported software</para>
- </listitem>
- </itemizedlist>
- <para> For additional information see <ulink url="http://www.jboss.com/products/devstudio"
- >JBoss.com</ulink></para>
- </section>
-
- <section id="JBossToolsInstall">
- <title>JBoss Tools Installation and Update</title>
- <para>This section covers the installation of the <property>JBoss Tools</property> modules.</para>
- <para><property>JBoss Tools</property> is an umbrella project for the JBoss developed plugins
- that are part of <property>JBoss Developer Studio</property>. The JBoss Tools modules are:</para>
- <itemizedlist>
- <listitem>
- <para>JBoss AS Tools</para>
- </listitem>
- <listitem>
- <para>Seam Tools</para>
- </listitem>
- <listitem>
- <para>Hibernate Tools</para>
- </listitem>
- <listitem>
- <para>Visual Page Editor</para>
- </listitem>
- <listitem>
- <para>JST Tools</para>
- </listitem>
- <listitem>
- <para>JBPM Tools</para>
- </listitem>
- <listitem>
- <para>Smooks Tools</para>
- </listitem>
- <listitem>
- <para>Deltacloud Tools</para>
- </listitem>
- </itemizedlist>
-
- <note>
- <title>Note</title>
- <para>The JBoss Tools Deltacloud component is not included with JBoss Developer Studio in this release.</para>
- </note>
-
- <para>To install the JBoss Tools plugins for Eclipse, you need the following:</para>
-
- <itemizedlist>
- <listitem>
- <para>A copy of Eclipse and Web Tools (make sure you have the
- <ulink url="http://www.jboss.org/community/wiki/Matrixofsupportedplatformsruntimesand...">appropriate version of Eclipse</ulink>).</para>
- </listitem>
- </itemizedlist>
- <para>The current version of JBoss Tools (3.2.0.GA) targets at Eclipse 3.6.1 Helios JEE Bundle which is available from <ulink url="http://www.eclipse.org/downloads/">eclipse.org</ulink>.</para>
-
- <note>
- <title>Tip:</title>
- <para>We recommend you do not use Eclipse.org update site to go from old version of Eclipse to new one.
- Instead we suggest that you download the full binary from <ulink url="http://www.eclipse.org/downloads/">here</ulink>.</para>
- </note>
-
- <para>If you can only use Eclipse 3.3 use <ulink url="http://www.jboss.org/tools/download.html">JBoss Tools 2.1.2</ulink>, but
- JBoss Tools 2.x will not have any of the new features.</para>
-
- <note>
- <title>Note:</title>
- <para>Remember to choose the download that matches your OS and use Java 6 when you run
- it.</para>
- </note>
- <para>If you need to install any standalone plug-in from JBoss Tools visit a <ulink url="http://community.jboss.org/wiki/InstallingJBossTools">JBoss Tools Wiki</ulink> page to read
- about dependencies between standalone plug-ins.</para>
- <para>For more information about how to install JBoss Tools 3.0 and JBoss Tools 3.1 please read the following docs:
- </para>
- <itemizedlist>
- <listitem><para><ulink url="https://www.jboss.org/tools/download/installation/update_3_0.html">JBoss Tools 3.0 Installation</ulink></para></listitem>
- <listitem><para><ulink url="https://www.jboss.org/tools/download/installation/update_3_1.html">JBoss Tools 3.1 Installation</ulink></para></listitem>
- </itemizedlist>
-
- <section>
- <title>Installation From Update Site</title>
-
-
- <para>Instead of downloading installation and updating manually, it's also possible to
- get the latest release of <property>JBoss Tools</property> from one of our update sites:
- <itemizedlist id="sites">
- <listitem>
- <para>Stable Updates: <ulink url="http://download.jboss.org/jbosstools/updates/stable"
- >http://download.jboss.org/jbosstools/updates/stable</ulink></para>
- </listitem>
- <listitem>
- <para> Development Updates: <ulink url="http://download.jboss.org/jbosstools/updates/development"
- >http://download.jboss.org/jbosstools/updates/development</ulink></para>
- </listitem>
- <listitem>
- <para> Nightly Builds: <ulink url="http://download.jboss.org/jbosstools/updates/nightly/trunk/"
- >http://download.jboss.org/jbosstools/updates/nightly/trunk/</ulink></para>
- </listitem>
- </itemizedlist>
- </para>
-<itemizedlist>
- <note>
- <title>Note:</title>
- <para>During the JBT installation and updating process using some of Jboss
- update sites the <emphasis>No repository found containing...</emphasis> error
- can appear. This is an Eclipse P2 bug. To work around it try: 1.Restarting Eclipse. 2.
- Add the update site again. 3. Performing the update again.</para>
- </note>
- <para>To install and/or update JBoss Tools from one of the update sites you should follow the steps:</para>
- <listitem><para>First, download the correct version of Eclipse
- for your platform which is compatible with the version of JBoss
- Tools you plan to install. For example if you want to install
- 3.2.0.GA Eclipse 3.6.1 Helios JEE Bundle is required.</para></listitem>
- <listitem><para>If you do not already have Java 5 or 6 installed and in your path,
- download and install it.</para></listitem>
- <listitem><para>When Eclipse is started, go to <itemizedlist>
- <listitem><para><menuchoice><guimenuitem>Help</guimenuitem><guimenuitem>Software Updates...</guimenuitem><guimenuitem>Available Software</guimenuitem><guimenuitem>Manage Sites...</guimenuitem><guimenuitem>Add...</guimenuitem></menuchoice><emphasis> (Eclipse 3.4)</emphasis></para></listitem>
- <listitem><para><menuchoice><guimenuitem>Help</guimenuitem><guimenuitem>Install New Software</guimenuitem><guimenuitem>Add...</guimenuitem></menuchoice><emphasis> (Eclipse 3.5, 3.6)</emphasis></para></listitem>
- </itemizedlist>
- </para></listitem>
- <listitem><para>After clicking the <guibutton>Add</guibutton> button the <property>Add Site</property> View should appear.
- In the <property>Location</property> field you should paste one of the update sites described
- <link linkend="sites">above</link>. On some platforms,
- you can also drag and drop the link from your browser directly into Eclipse. In the <property>Name</property> field you can enter any name you like.
- In the end press the <guibutton>OK</guibutton> button.</para>
- <figure>
- <title>Add Update Site</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/getting_started/getting_started_4a.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- </listitem>
- <listitem id="from_point"><para>In the <property>Install</property> View select features to install, then click the <guibutton>Next</guibutton> button.</para>
- <figure>
- <title>JBoss Tools installation</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/getting_started/getting_started_4b.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- </listitem>
- <listitem>
- <para>And the system checks whether all necessary requirements and
- dependencies are installed on your Eclipse.</para>
- <figure>
- <title>Requirements and
- dependencies check</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/getting_started/getting_started_10.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- <para>If some of the dependencies are missing an error message will appear and
- the installation process will be terminated.
- </para>
- <note>
- <title>Note:</title>
- <para>Sometimes when a user changes the list of plugins for download and clicks
- <guibutton>Next</guibutton>, after the required dependences have been checked,
- the list of missing dependencies from the previous attempt is showed.
- In this case completely closing the <emphasis>Install New Software</emphasis> dialog can help.</para>
- </note>
- <para>If JBoss Tools are already installed on your Eclipse and you are performing an update (and not installing new components) the following messages may appear in your <emphasis>Details</emphasis> section.
- Ignore them and press the <guibutton>Next</guibutton> button.</para>
- <figure>
- <title>Possible messages</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/getting_started/getting_started_4c.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- </listitem>
- <listitem><para>When you click the <guibutton>Finish</guibutton> button the Installation and/or Updating process will commence.</para></listitem>
- <listitem><para>Once the installation is complete, restart Eclipse when prompted.</para>
- <figure>
- <title>Message dialog</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/getting_started/getting_started_4d.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- </listitem>
- <listitem><para>After fetching all the features and plugins for installation,
- you may be warned that your selection contains unsigned jars.
- This is normal, simply accept the warning and continue. </para>
- <figure>
- <title>Warning Message</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/getting_started/getting_started_4e.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- </listitem>
-</itemizedlist>
-
- <note>
- <title>Note:</title>
- <para>While installing JBoss Tools on GNU/Linux (64-bit) through the eclipse installation manager you may run into some problems which can interrupt your installation process.
- Please, read the
- <ulink url="http://www.jboss.org/community/wiki/ManualinstallationofJBossTools31xonEc...">Manual installation of JBoss Tools 3.1.x on Eclipse 3.5 on GNU/Linux (64-bit)</ulink>
- wiki article which provides you with the necessary steps to do it correct.</para>
- </note>
- </section>
- <section>
- <title>Installation From Zip file</title>
-
- <para>It is also possible to install JBoss Tools using the Eclipse P2 update manager and a common zip file which provides a single installer for all platforms.</para>
- <para>You can download JBoss Tools in a zip file from one of the pages below:</para>
- <itemizedlist id="zip_sites">
- <listitem>
- <para>Stable Releases: <ulink url="http://www.jboss.org/tools/download/stable.html"
- >http://www.jboss.org/tools/download/stable.html</ulink></para>
- </listitem>
- <listitem>
- <para> Development Updates: <ulink url="http://www.jboss.org/tools/download/dev.html"
- >http://www.jboss.org/tools/download/dev.html</ulink></para>
- </listitem>
- <listitem>
- <para> Nightly Builds: <ulink url="http://download.jboss.org/jbosstools/updates/nightly/"
- >http://download.jboss.org/jbosstools/updates/nightly/</ulink></para>
- </listitem>
- </itemizedlist>
- <para>When you downloaded Jboss Tools Zip please <emphasis>DO NOT UNZIP IT</emphasis> and follow the steps described below:</para>
- <itemizedlist>
- <listitem><para>When Eclipse is started, go to <menuchoice><guimenuitem>Help</guimenuitem><guimenuitem>Install New Software...</guimenuitem><guimenuitem>Add...</guimenuitem><guimenuitem>Archive...</guimenuitem></menuchoice></para></listitem>
- <listitem><para>Browse for the update site zip. In the <emphasis>Name</emphasis> field you can write any name you like.
- Then click the <guibutton>OK</guibutton> button.</para>
- <figure>
- <title>Installation from a zip file</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/getting_started/getting_started_4f.png"/>
- </imageobject>
- </mediaobject>
- </figure>
- </listitem>
- <listitem><para>The remaining steps are the same as described in the section <link linkend="from_point">
- Installation From Update Site section</link>. </para>
- </listitem>
- </itemizedlist>
-
- </section>
-
- </section>
- </section>
-
- <section id="Welcome">
- <title>Welcome to JBoss Developer Studio</title>
- <para>In this section we'll show you how to work with the welcome page of the <property>JBoss
- Developer Studio</property>.</para>
- <para>The welcome page is the first page you see when you first launch <property>JBoss Developer
- Studio</property>. </para>
-
- <figure>
- <title>Welcome to JBoss Developer Studio</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/getting_started/getting_started_5.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>With the help of its page you will be able:</para>
- <itemizedlist>
- <listitem>
- <para>to get quick access to Getting Started Documentation (guides, tutorials and
- viewlets)</para>
- </listitem>
- </itemizedlist>
-
- <figure>
- <title>Getting Started Documentation</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/getting_started/getting_started_6.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <itemizedlist>
- <listitem>
- <para>to create new Seam projects, jBPM Process, JSF or Struts projects using JBDS
- wizards</para>
- </listitem>
- </itemizedlist>
-
- <figure>
- <title>Create New...</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/getting_started/getting_started_7.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <itemizedlist>
- <listitem>
- <para>to get short descriptions of the perspectives that JBDS provides</para>
- </listitem>
- </itemizedlist>
-
- <figure>
- <title>Perspectives</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/getting_started/getting_started_8.png"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <itemizedlist>
- <listitem>
- <para>to visit JBoss Developer Studio web resources.</para>
- </listitem>
- </itemizedlist>
-
- <figure>
- <title>Web Resources</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/getting_started/getting_started_9.png" scale="90"/>
- </imageobject>
- </mediaobject>
- </figure>
-
- <para>You can start working with <property>JBoss Developer Studio</property> by clicking on <emphasis>
- <property>Workbench</property>
- </emphasis> button or simply closing the Welcome page.</para>
-
- </section>
-
- <section id="Upgrading">
- <?dbhtml filename="Upgrading.html"?>
- <title>Upgrading</title>
- <para>Because JBDS 3.0x and 4.0 use different versions of Eclipse, it is not possible to directly upgrade from an older version to JBDS 4.0.</para>
- <note>
- <title>Tip</title>
- <para>It is possible to run JBDS 3.0x and 4.0 side by side, as long as they have been installed into separate directories.</para>
- </note>
-
- </section>
-
- <section id="Uninstalling">
- <?dbhtml filename="Uninstalling.html"?>
- <title>Uninstalling</title>
- <itemizedlist>
- <listitem>
- <para>Make sure <property>JBoss Developer Studio</property> is not running</para>
- </listitem>
- <listitem>
- <para>Uninstall your current version of <property>JBoss Developer Studio</property> by running the Uninstaller</para>
- </listitem>
- </itemizedlist>
- </section>
-
- <section id="Usage_Reporting">
- <title>Usage Reporting</title>
- <para>
+ <section id="Usage_Reporting">
+ <title>Usage Reporting</title>
+ <para>
The JBoss Developer Studio now includes a usage plug-in that anonymously reports information back to JBoss. The plug-in is not enabled by default. To enable, make sure the <guilabel>Report usage of JBoss Tools to JBoss Tools team.</guilabel> box is ticked.
- </para>
-
- <figure>
- <title>Usage plug-in pop-up</title>
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/getting_started/usage_plug-in_1_JBDS.png"/>
- </imageobject>
- </mediaobject>
- </figure>
+ </para>
- <para>
- Once enabled, the plug-in will remain active until turned off. To turn the active plug-in off, navigate to <menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Preferences</guimenuitem><guimenuitem>JBoss Tools</guimenuitem><guimenuitem>Usage Reporting</guimenuitem></menuchoice>.
- </para>
- <para>
+ <figure>
+ <title>Usage plug-in pop-up</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/getting_started/usage_plug-in_1_JBDS.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <para>
+ Once enabled, the plug-in will remain active until turned off. To turn the active plug-in off, navigate to <menuchoice><guimenuitem>Window</guimenuitem>
+ <guimenuitem>Preferences</guimenuitem>
+ <guimenuitem>JBoss Tools</guimenuitem>
+ <guimenuitem>Usage Reporting</guimenuitem>
+ </menuchoice>.
+ </para>
+ <para>
The gathered data allows JBoss to see how the tools are being used and where they are being used geographically. Currently we are looking into the operating systems being used, screen resolution and how often the tooling environment is started. In the future geographic information will assist in focussing translation resources to areas where the developer environment is most used.
- </para>
- <para>
+ </para>
+ <para>
The plug-in uses Google Analytics to track and report data by acting as if you were visiting the site http://jboss.org/tools/usage/. To view the type of information being collected, refer to <xref linkend="Collected_usage_information_guide"/>.
- </para>
- <para>
+ </para>
+ <para>
To view the source code of the usage plug-in visit <ulink url="http://anonsvn.jboss.org/repos/jbosstools/trunk/usage/">http://anonsvn.jboss.org/repos/jbosstools/trunk/usage/</ulink>.
- </para>
- <section id="Collected_usage_information_guide">
- <title>Collected usage information guide</title>
- <para>
- Below you will find an outline of the information that is reported and the Goolge Analytics fields that are used to gather this information.
- </para>
- <variablelist>
- <varlistentry>
- <term>Version</term>
- <listitem>
- <para>
- The <guilabel>Content</guilabel> field has been modified to report the installed JBoss Developer Studio version. Sample returned values include: jbdevstudio-linux-gtk-x86_64-4.0.0.v201009301221R-H20-Beta1.jar and jbdevstudio-linux-gtk-3.0.2.v201009161622R-H138-GA.jar.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Installed components</term>
- <listitem>
- <para>
- The <guilabel>Keyword</guilabel> field has been modified to report the installed JBoss Developer Studio components. Sample returned values include: JBoss AS, Drools, Teiid and ModeShape.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Visitor type</term>
- <listitem>
- <para>
- The <guilabel>Visitor type</guilabel> field reports if the current user is new or returning.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Language</term>
- <listitem>
- <para>
- The <guilabel>Language</guilabel> field reports the localized language the product is being used in. Sample returned values include: en-US, de-DE and fr-FR.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Location fields</term>
- <listitem>
- <para>
- The location fields report the geographical location where the product is being used based on the continent, country and city. Sample returned values include: Europe (continent), Germany (country) and Munich (city).
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Eclipse interface and version</term>
- <listitem>
- <para>
- The <guilabel>Browser</guilabel> field has been modified to report the Eclipse interface and version being used. Sample returned values include: JBoss Developer Studio: 3.0.0 and JBoss Developer Studio: 3.0.1.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Operating System</term>
- <listitem>
- <para>
- The <guilabel>Operating System</guilabel> field reports the Operating System and its version that the product is running on (with Linux distribution version reporting conducted through the <guilabel>User Defined Value</guilabel> field). Sample returned values include: Linux, Macintosh 10.4, Macintosh 10.6, Windows XP and Windows 7.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Linux distribution version</term>
- <listitem>
- <para>
- The <guilabel>User Defined Value</guilabel> field reports the distribution and version of Linux, if one is being used as the Operating System. Sample returned values include: Red Hat Enterprise Linux 5.4 and Fedora 13.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Screen colors</term>
- <listitem>
- <para>
- The <guilabel>Screen colors</guilabel> field reports the color depth being used. Sample returned values include: 32-bit and 24-bit.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Screen resolution</term>
- <listitem>
- <para>
- The <guilabel>Screen resolution</guilabel> field reports the resolution being used. Sample returned values include: 2048x1536 and 1920x1080.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Java version</term>
- <listitem>
- <para>
- The <guilabel>Flash version</guilabel> field has been modified to report the Java version used. Sample returned values include: 1.6.0_20 and 1.5.0_9.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Connection speed</term>
- <listitem>
- <para>
- The <guilabel>Connection speed</guilabel> field reports the type of internet connection being used. Sample returned values include: T1, Cable and DSL.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- </section>
- </section>
+ </para>
+ <section id="Collected_usage_information_guide">
+ <title>Collected usage information guide</title>
+ <para>
+ Below you will find an outline of the information that is reported and the Goolge Analytics fields that are used to gather this information.
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Version</term>
+ <listitem>
+ <para>
+ The <guilabel>Content</guilabel> field has been modified to report the installed JBoss Developer Studio version. Sample returned values include: jbdevstudio-linux-gtk-x86_64-4.0.0.v201009301221R-H20-Beta1.jar and jbdevstudio-linux-gtk-3.0.2.v201009161622R-H138-GA.jar.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Installed components</term>
+ <listitem>
+ <para>
+ The <guilabel>Keyword</guilabel> field has been modified to report the installed JBoss Developer Studio components. Sample returned values include: JBoss AS, Drools, Teiid and ModeShape.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Visitor type</term>
+ <listitem>
+ <para>
+ The <guilabel>Visitor type</guilabel> field reports if the current user is new or returning.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Language</term>
+ <listitem>
+ <para>
+ The <guilabel>Language</guilabel> field reports the localized language the product is being used in. Sample returned values include: en-US, de-DE and fr-FR.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Location fields</term>
+ <listitem>
+ <para>
+ The location fields report the geographical location where the product is being used based on the continent, country and city. Sample returned values include: Europe (continent), Germany (country) and Munich (city).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Eclipse interface and version</term>
+ <listitem>
+ <para>
+ The <guilabel>Browser</guilabel> field has been modified to report the Eclipse interface and version being used. Sample returned values include: JBoss Developer Studio: 3.0.0 and JBoss Developer Studio: 3.0.1.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Operating System</term>
+ <listitem>
+ <para>
+ The <guilabel>Operating System</guilabel> field reports the Operating System and its version that the product is running on (with Linux distribution version reporting conducted through the <guilabel>User Defined Value</guilabel> field). Sample returned values include: Linux, Macintosh 10.4, Macintosh 10.6, Windows XP and Windows 7.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Linux distribution version</term>
+ <listitem>
+ <para>
+ The <guilabel>User Defined Value</guilabel> field reports the distribution and version of Linux, if one is being used as the Operating System. Sample returned values include: Red Hat Enterprise Linux 5.4 and Fedora 13.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Screen colors</term>
+ <listitem>
+ <para>
+ The <guilabel>Screen colors</guilabel> field reports the color depth being used. Sample returned values include: 32-bit and 24-bit.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Screen resolution</term>
+ <listitem>
+ <para>
+ The <guilabel>Screen resolution</guilabel> field reports the resolution being used. Sample returned values include: 2048x1536 and 1920x1080.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Java version</term>
+ <listitem>
+ <para>
+ The <guilabel>Flash version</guilabel> field has been modified to report the Java version used. Sample returned values include: 1.6.0_20 and 1.5.0_9.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Connection speed</term>
+ <listitem>
+ <para>
+ The <guilabel>Connection speed</guilabel> field reports the type of internet connection being used. Sample returned values include: T1, Cable and DSL.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
+ </section>
- <section id="Support">
- <?dbhtml filename="Support.html"?>
- <title>Support</title>
- <para>If you have comments or questions, you can discuss them on our <ulink url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=258">JBoss
- Developer Studio Forum</ulink>.</para>
- <para>When posting questions to the forum, please include the following information:</para>
- <orderedlist>
- <listitem>
- <para>JBoss Developer Studio version</para>
- </listitem>
- <listitem>
- <para>Exact error message</para>
- </listitem>
- <listitem>
- <para>Steps to reproduce the issue</para>
- </listitem>
- </orderedlist>
+ <section id="Support">
+ <?dbhtml filename="Support.html"?>
+ <title>Support</title>
+ <para>
+ If you have comments or questions, you can discuss them on our <ulink url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=258">JBoss Developer Studio Forum</ulink>.
+ </para>
+ <para>When posting questions to the forum, please include the following information:</para>
+ <orderedlist>
+ <listitem>
+ <para>JBoss Developer Studio version</para>
+ </listitem>
+ <listitem>
+ <para>Exact error message</para>
+ </listitem>
+ <listitem>
+ <para>Steps to reproduce the issue</para>
+ </listitem>
+ </orderedlist>
- <para><property>JBDS</property> subscribers can get additional support on our <ulink url="https://network.jboss.com/jbossnetwork/login.html">Support Portal</ulink>.</para>
- </section>
+ <para>
+ <property>JBDS</property> subscribers can get additional support on our <ulink url="https://network.jboss.com/jbossnetwork/login.html">Support Portal</ulink>.
+ </para>
+ </section>
- <section id="OtherRelevantResourcesOnTheTopic33">
- <?dbhtml filename="OtherRelevantResourcesOnTheTopic33.html"?>
- <title>Other relevant resources on the topic</title>
- <para>JBDS on RedHat: <ulink url="http://www.redhat.com/developer_studio">JBoss Developer
- Studio</ulink></para>
- <para>Forum: <ulink url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=258">JBoss
- Forum</ulink></para>
- <para>
- Wiki: <ulink url="http://www.jboss.org/community/wiki/JBossTools"> JBossToolsWiki </ulink>
- </para>
- <para>Subscription: <ulink url="https://www.redhat.com/apps/store/developers/jboss_developer_studio.html">JBDS
- Subscription</ulink></para>
-
- <para>The latest documentation builds are available <ulink url="http://download.jboss.org/jbosstools/nightly-docs/">here</ulink>.</para>
-
- <para>
- <ulink url="http://www.jboss.org/community/wiki/Matrixofsupportedplatformsruntimesand...">Matrix of supported platforms, runtimes and technologies in JBossTools/JBDS</ulink></para>
- </section>
+ <section id="OtherRelevantResourcesOnTheTopic33">
+ <?dbhtml filename="OtherRelevantResourcesOnTheTopic33.html"?>
+ <title>Other relevant resources on the topic</title>
+ <para>JBDS on RedHat: <ulink url="http://www.redhat.com/developer_studio">JBoss Developer
+ Studio</ulink>
+ </para>
+ <para>Forum: <ulink url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=258">JBoss Forum</ulink></para>
+ <para>Wiki: <ulink url="http://www.jboss.org/community/wiki/JBossTools"> JBossToolsWiki </ulink></para>
+ <para>Subscription: <ulink url="https://www.redhat.com/apps/store/developers/jboss_developer_studio.html">JBDS Subscription</ulink></para>
+ <para>The latest documentation builds are available <ulink url="http://download.jboss.org/jbosstools/nightly-docs/">here</ulink>.</para>
+ <para>
+ <ulink url="http://www.jboss.org/community/wiki/Matrixofsupportedplatformsruntimesand...">Matrix of supported platforms, runtimes and technologies in JBossTools/JBDS</ulink>
+ </para>
+ </section>
</chapter>
Added: trunk/documentation/guides/GettingStartedGuide/en-US/installation.xml
===================================================================
--- trunk/documentation/guides/GettingStartedGuide/en-US/installation.xml (rev 0)
+++ trunk/documentation/guides/GettingStartedGuide/en-US/installation.xml 2011-01-19 00:36:28 UTC (rev 28375)
@@ -0,0 +1,674 @@
+<chapter id="installation">
+ <?dbhtml filename="getting_started.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>Installing JBoss Developer Studio</title>
+
+ <section id="ConfigJavaEnvironment">
+ <?dbhtml filename="ConfigJavaEnvironment.html"?>
+ <title>Configuring Your Java Environment</title>
+ <para>
+ You must have a working installation of JDK before you install <property>JBoss Developer Studio</property>. Thus in this guide we will show you how to install a 32-bit Sun JDK 5.0 on a Linux Platform and Microsoft Windows Platform.
+ </para>
+
+ <section id="InstallJDK50onLinux">
+ <title>Installing and Configuring 32-bit Sun JDK 5.0 on Linux</title>
+ <para>To install 32-bit Sun JDK 5.0 on Linux and configure it, you should follow the next steps:</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Download the <ulink url="http://java.sun.com/javase/downloads/index_jdk5.jsp">Sun JDK 5.0 (Java 2 Development Kit)</ulink> from Sun's website. Choose "JDK 5.0 Update <x>" (where "x" is the latest update number) for download and then select "Red Hat Package Manager in self-extracting" file for Linux. Read the instructions on Sun's website for installing the JDK.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ If you don't want to use SysV service scripts you can install the "self-extracting file" for Linux instead of choosing the "RPM in self-extracting" file. In that case you can skip the next step mentioned here. But it is recommended to use the SysV service scripts for production servers.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Download and install the appropriate -compat RPM from JPackage <ulink url="ftp://jpackage.hmdc.harvard.edu/JPackage/1.7/generic/RPMS.non-free/">here</ulink>. Please ensure you choose a matching version of the -compat package to the JDK you've installed.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Create an environment variable that points to the JDK installation directory and call it JAVA_HOME. Add <emphasis><property>$JAVA_HOME/bin</property></emphasis> to the system path to be able to run java from the command line. You can do this by adding the following lines to the .bashrc file in your home directory.
+ </para>
+ <programlisting><![CDATA[#In this example /usr/java/jdk1.5.0_11 is the JDK installation directory.
+export JAVA_HOME=/usr/java/jdk1.5.0_11
+export PATH=$PATH:$JAVA_HOME/bin]]></programlisting>
+ </listitem>
+ </itemizedlist>
+
+ <note>
+ <title>Note:</title>
+
+ <para>
+ If you have JDK already installed and added in your system path, you should add <emphasis>$JAVA_HOME/bin</emphasis> before the old <emphasis>$PATH</emphasis> (not after it) so that the new version of JDK can be found first, i. e. <emphasis>export PATH=$JAVA_HOME/bin:$PATH</emphasis> This way, the machine will pick up the new JVM first. You only 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 also for the user account that will run the server.</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ If you have more than one version of JVM installed on your machine, make sure you are using the JDK 1.5 installation as the default java and javac. You can do this using the alternatives system. The alternatives system allows different versions of Java from different sources to co-exist on your system.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <section id="SelectAlternativesforJava">
+ <title>Select alternatives for java, javac and java_sdk_1.5.0</title>
+ <itemizedlist>
+ <listitem>
+ <para>As a root user, type the following command at the shell prompt and you should see something like this:</para>
+ </listitem>
+ </itemizedlist>
+ <programlisting><![CDATA[[root@vsr ~]$ /usr/sbin/alternatives --config java
+There are 2 programs that provide 'java'.
+Selection Command
+-----------------------------------------------
+ 1 /usr/lib/jvm/jre-1.4.2-gcj/bin/java
+*+ 2 /usr/lib/jvm/jre-1.5.0-sun/bin/java
+Enter to keep the current selection[+], or type selection number:]]></programlisting>
+ <para>
+ Make sure the Sun version [jre-1.5.0-sun in this case] is selected (marked with a '+' in the output), or select it by entering its number as prompted.
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>Repeat the same for javac and java_sdk_1.5.0.</para>
+ </listitem>
+ </itemizedlist>
+ <programlisting><![CDATA[[root@vsr ~]$ /usr/sbin/alternatives --config javac
+There is 1 program that provides 'javac'.
+ Selection Command
+-----------------------------------------------
+*+ 1 /usr/lib/jvm/java-1.5.0-sun/bin/javac
+Enter to keep the current selection[+], or type selection number:
+
+[root@vsr ~]$ /usr/sbin/alternatives --config java_sdk_1.5.0
+There is 1 program that provide 'java_sdk_1.5.0'.
+ Selection Command
+-----------------------------------------------
+*+ 1 /usr/lib/jvm/java-1.5.0-sun
+Enter to keep the current selection[+], or type selection number:]]></programlisting>
+ <para>You should verify that java, javac and java_sdk_1.5.0 all point to the same manufacturer and version.</para>
+ <note>
+ <title>Note:</title>
+ <para>You can always override this step by setting the JAVA_HOME environment variable as explained in the previous step.</para>
+ </note>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Make sure that the java executable is in your path and that you are using an appropriate version. To verify your Java environment, type "java -version" at the shell prompt and you should see something like this:
+ </para>
+ </listitem>
+ </itemizedlist>
+ <programlisting><![CDATA[[root@vsr ~]$ java -version
+java version "1.5.0_11"
+Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
+Java HotSpot(TM) Client VM (build 1.5.0_11-b03, mixed mode, sharing)]]></programlisting>
+ </section>
+
+ </section>
+ <section id="InstallJDK50onWindows">
+ <title>Installing and Configuring 32-bit Sun JDK 5.0 on Microsoft Windows</title>
+
+ <para>To install and configure 32-bit Sun JDK 5.0 on Microsoft Windows, follow these steps:</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Download the <ulink url="http://java.sun.com/javase/downloads/index_jdk5.jsp">Sun JDK 5.0 (Java 2 Development Kit)</ulink> from Sun's website. Choose "JDK 5.0 Update <x>" (where "x" is the latest update number) for download and then select your Windows Platform options to perform the installation.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Create an environment variable called JAVA_HOME that points to the JDK installation directory, for example: <emphasis>C:\Program Files\Java\jdk1.5.0_11\</emphasis>
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>In order to run java from the command line, add the <emphasis>jre\bin</emphasis> directory
+ to your path, for example:</para>
+ <para>
+ <emphasis>C:\Program Files\Java\jdk1.5.0_11\jre\bin</emphasis>
+ </para>
+ <para>To do this, open the <emphasis>
+ <property>Control Panel</property>
+ </emphasis> from the <emphasis>
+ <property>Start</property>
+ </emphasis> menu, switch to Classic View if necessary, open the System Control Panel applet (<emphasis>
+ <property>System</property>
+ </emphasis>), select the <emphasis>
+ <property>Advanced</property>
+ </emphasis> Tab, and click on the <emphasis>
+ <property>Environment Variables</property>
+ </emphasis> button.</para>
+ <para>Now, when 32-bit Sun JDK 5.0 has been successfully installed, we can pass on to the next
+ step.</para>
+ </section>
+
+ </section>
+
+ <section id="InstallingJBDS">
+ <?dbhtml filename="InstallingRHDS.html"?>
+ <title>JBoss Developer Studio Installation</title>
+
+ <para>This chapter will provide you with detailed information on how to install <property>JBoss Developer Studio</property>.</para>
+
+ <para>
+ JBDS comes with a simple installer, bundled with tested and pre-configured versions of Eclipse, WTP, JBossEAP, Seam, and SpringIDE. The following steps show you how to install JBDS:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ First of all you need the appropriate installation file for your platform from <ulink url="https://www.redhat.com/apps/store/developers/jboss_developer_studio.html">Red Hat website</ulink>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Run the following command in a terminal window:</para>
+ <programlisting role="JAVA"><![CDATA[java -jar jbdevstudio-eap-linux-gtk-4.0.0.GA.jar]]></programlisting>
+ </listitem>
+ <listitem>
+ <para>Follow the instructions presented by the installation wizard:</para>
+ </listitem>
+ </itemizedlist>
+
+ <figure>
+ <title>JBoss Developer Studio Installation Wizard</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/getting_started/getting_started_1.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <itemizedlist>
+ <listitem>
+ <para>Provide the installation path</para>
+ </listitem>
+ <listitem>
+ <para>Select the appropriate Java Virtual Machine</para>
+ </listitem>
+ </itemizedlist>
+
+ <note>
+ <title>Tip:</title>
+ <para>
+ By selecting <emphasis><property>Default Java VM</property></emphasis> you set default Java VM of your system (to verify your Java environment, type "java -version" in console).
+ </para>
+ </note>
+
+ <para>Selecting <emphasis>
+ <property>Specific Java VM</property>
+ </emphasis> you can provide the path to non-default Java VM.</para>
+
+ <note>
+ <title>Note:</title>
+ <para>
+ JBoss Developer Studio 4.0 comes integrated with JBoss EAP 5.1 that requires JDK 6.0 to run and "gij" isn't available on every platform.
+ </para>
+ </note>
+
+ <figure>
+ <title>Select Java VM</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/getting_started/getting_started_2.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ As part of the installation you can choose to install <ulink url="http://www.jboss.com/products/platforms/application">JBoss Enterprise Application Platform</ulink>. Select <emphasis><property>Yes</property></emphasis> to use it in JBoss Developer Studio.
+ </para>
+ <note>
+ <title>Note:</title>
+ <para>Like in the previous version of JBDS, JBDS 4.0.0.GA comes integrated with JBoss EAP 5.1 that supports EAP 5 adapter and Seam 2.2.</para>
+ </note>
+
+ <para>This step lets you configure locally available JBoss Application Servers: </para>
+ </listitem>
+ </itemizedlist>
+
+ <figure>
+ <title>JBoss Enterprise Application Platform Installing</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/getting_started/getting_started_3.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ You can fill the list automatically using the <guibutton>Find</guibutton> button. When the <guibutton>Find</guibutton> button is clicked you are propmpted to select the folder from which to search for available JBoss Application Servers. Click the <guibutton>OK</guibutton> button to select the chosen folder.
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <figure>
+ <title>Finding Servers in the Selected Directory</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/getting_started/getting_started_3_3_1.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para/>
+
+ <itemizedlist>
+ <listitem>
+ <para> All available servers in the selected directory will be added to the list with the following details: Name, Type, Version and Location.</para>
+ </listitem>
+ </itemizedlist>
+
+ <itemizedlist>
+ <listitem>
+ <para>You can also add servers one by one using the <guibutton>Add</guibutton> button:</para>
+ </listitem>
+ </itemizedlist>
+
+ <figure>
+ <title>Add Server to be Configured</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/getting_started/getting_started_3_1.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para/>
+
+ <para>
+ Click on the <guibutton>Browse</guibutton> button and select the server location. Fields Name, Type and Version will be filled in automatically:
+ </para>
+
+ <figure>
+ <title>Specify Server Location</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/getting_started/getting_started_3_2.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para/>
+
+ <para>When you click the <guibutton>OK</guibutton> button the server will be added to the list with the details on its type, version and location.</para>
+
+ <para>
+ The <guibutton>Remove</guibutton> button will the remove the selected server from the list. If necessary, you can edit the server details clicking on the <guibutton>Edit</guibutton> button:
+ </para>
+
+ <figure>
+ <title>Edit Server</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/getting_started/getting_started_3_4.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para/>
+
+ <!-- <note>
+ <title>Note:</title>
+ <para>The installer installs JBoss Enterprise Application Platform for running your applications
+ if you select this option during the installation process. If you want to use a different server
+ than ours, you can change the setting in JBoss Developer Studio.</para>
+ </note>-->
+
+ <itemizedlist>
+ <listitem>
+ <para>Click the <guibutton>Next</guibutton> button to bring up a summary page where you can check your installation paths and see the components that will be installed. If you'd like to change something, press the <guibutton>Previous</guibutton> button. Click the <guibutton>Next</guibutton> button to start installation. </para>
+ </listitem>
+ </itemizedlist>
+
+ <para/>
+
+ <figure>
+ <title>Summary Information</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/getting_started/getting_started_4.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+
+ </section>
+
+ <section id="jbds_jbosstools">
+
+ <title>JBoss Developer Studio and JBoss Tools</title>
+
+ <para>
+ This section highlights the differences between <property>JBoss Developer Studio</property> and <property>JBoss Tools</property>, and provides the steps on the <property>JBoss Tools</property> installation process.
+ </para>
+
+ <section id="WhatDifferenceBetweenJBDSAndJBossTools">
+ <title>What is the difference?</title>
+
+ <para>
+ <property>JBoss Tools</property> is a component of <property>JBoss Developer Studio</property>, which is designed to be an easy-to-install Eclipse based IDE, fully configured and ready to run with the bundled <property>JBoss Enterprise Application Platform</property>.
+ </para>
+
+ <para>In short <property>JBoss Tools</property> are just a set of Eclipse plugins and <property>JBoss Developer Studio</property> adds:</para>
+ <itemizedlist>
+ <listitem>
+ <para>An installer</para>
+ </listitem>
+ <listitem>
+ <para>Eclipse and Web Tools preconfigured</para>
+ </listitem>
+ <listitem>
+ <para>JBoss EAP with JBoss AS and Seam preconfigured</para>
+ </listitem>
+ <listitem>
+ <para>3rd party plugins bundled and configured</para>
+ </listitem>
+ <listitem>
+ <para>Access to RHEL and Red Hat Network</para>
+ </listitem>
+ <listitem>
+ <para>Access to the JBoss/Red Hat supported software</para>
+ </listitem>
+ </itemizedlist>
+ <para> For additional information see <ulink url="http://www.jboss.com/products/devstudio">JBoss.com</ulink>
+ </para>
+ </section>
+
+ <section id="JBossToolsInstall">
+ <title>JBoss Tools Installation and Update</title>
+ <para>This section covers the installation of the <property>JBoss Tools</property> modules.</para>
+ <para>
+ <property>JBoss Tools</property> is an umbrella project for the JBoss developed plugins that are part of <property>JBoss Developer Studio</property>. The JBoss Tools modules are:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>JBoss AS Tools</para>
+ </listitem>
+ <listitem>
+ <para>Seam Tools</para>
+ </listitem>
+ <listitem>
+ <para>Hibernate Tools</para>
+ </listitem>
+ <listitem>
+ <para>Visual Page Editor</para>
+ </listitem>
+ <listitem>
+ <para>JST Tools</para>
+ </listitem>
+ <listitem>
+ <para>JBPM Tools</para>
+ </listitem>
+ <listitem>
+ <para>Smooks Tools</para>
+ </listitem>
+ <listitem>
+ <para>Deltacloud Tools</para>
+ </listitem>
+ </itemizedlist>
+
+ <note>
+ <title>Note</title>
+ <para>The JBoss Tools Deltacloud component is not included with JBoss Developer Studio in this release.</para>
+ </note>
+
+ <para>To install the JBoss Tools plugins for Eclipse, you need the following:</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ A copy of Eclipse and Web Tools (make sure you have the <ulink url="http://www.jboss.org/community/wiki/Matrixofsupportedplatformsruntimesand...">appropriate version of Eclipse</ulink>).
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ The current version of JBoss Tools (3.2.0.GA) targets at Eclipse 3.6.1 Helios JEE Bundle which is available from <ulink url="http://www.eclipse.org/downloads/">eclipse.org</ulink>.
+ </para>
+
+ <note>
+ <title>Tip:</title>
+ <para>
+ We recommend you do not use Eclipse.org update site to go from old version of Eclipse to new one. Instead we suggest that you download the full binary from <ulink url="http://www.eclipse.org/downloads/">here</ulink>.
+ </para>
+ </note>
+
+ <para>
+ If you can only use Eclipse 3.3 use <ulink url="http://www.jboss.org/tools/download.html">JBoss Tools 2.1.2</ulink>, but JBoss Tools 2.x will not have any of the new features.
+ </para>
+
+ <note>
+ <title>Note:</title>
+ <para>Remember to choose the download that matches your OS and use Java 6 when you run it.</para>
+ </note>
+ <para>
+ If you need to install any standalone plug-in from JBoss Tools visit a <ulink url="http://community.jboss.org/wiki/InstallingJBossTools">JBoss Tools Wiki</ulink> page to read about dependencies between standalone plug-ins.
+ </para>
+ <para>For more information about how to install JBoss Tools 3.0 and JBoss Tools 3.1 please read the following docs:</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <ulink url="https://www.jboss.org/tools/download/installation/update_3_0.html">JBoss Tools 3.0 Installation</ulink>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <ulink url="https://www.jboss.org/tools/download/installation/update_3_1.html">JBoss Tools 3.1 Installation</ulink>
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <section>
+ <title>Installation From Update Site</title>
+ <para>
+ Instead of downloading installation and updating manually, it's also possible to get the latest release of <property>JBoss Tools</property> from one of our update sites:
+ <itemizedlist id="sites">
+ <listitem>
+ <para>Stable Updates: <ulink url="http://download.jboss.org/jbosstools/updates/stable">http://download.jboss.org/jbosstools/updates/stable</ulink>
+ </para>
+ </listitem>
+ <listitem>
+ <para> Development Updates: <ulink url="http://download.jboss.org/jbosstools/updates/development">http://download.jboss.org/jbosstools/updates/development</ulink>
+ </para>
+ </listitem>
+ <listitem>
+ <para> Nightly Builds: <ulink url="http://download.jboss.org/jbosstools/updates/nightly/trunk/">http://download.jboss.org/jbosstools/updates/nightly/trunk/</ulink>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ <itemizedlist>
+ <note>
+ <title>Note:</title>
+ <para>
+ During the JBT installation and updating process using some of JBoss update sites the <emphasis>No repository found containing...</emphasis> error can appear. This is an Eclipse P2 bug. To work around it try: 1.Restarting Eclipse. 2. Add the update site again. 3. Performing the update again.
+ </para>
+ </note>
+ <para>To install and/or update JBoss Tools from one of the update sites you should follow the steps:</para>
+ <listitem>
+ <para>
+ First, download the correct version of Eclipse for your platform which is compatible with the version of JBoss Tools you plan to install. For example if you want to install 3.2.0.GA Eclipse 3.6.1 Helios JEE Bundle is required.
+ </para>
+ </listitem>
+ <listitem>
+ <para>If you do not already have Java 5 or 6 installed and in your path, download and install it.</para>
+ </listitem>
+ <listitem>
+ <para>When Eclipse is started, go to
+ <itemizedlist>
+ <listitem>
+ <para>
+ <menuchoice><guimenuitem>Help</guimenuitem>
+ <guimenuitem>Software Updates...</guimenuitem>
+ <guimenuitem>Available Software</guimenuitem>
+ <guimenuitem>Manage Sites...</guimenuitem>
+ <guimenuitem>Add...</guimenuitem>
+ </menuchoice>
+ <emphasis> (Eclipse 3.4)</emphasis>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <menuchoice>
+ <guimenuitem>Help</guimenuitem>
+ <guimenuitem>Install New Software</guimenuitem>
+ <guimenuitem>Add...</guimenuitem>
+ </menuchoice>
+ <emphasis> (Eclipse 3.5, 3.6)</emphasis>
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ After clicking the <guibutton>Add</guibutton> button the <property>Add Site</property> View should appear. In the <property>Location</property> field you should paste one of the update sites described <link linkend="sites">above</link>. On some platforms, you can also drag and drop the link from your browser directly into Eclipse. In the <property>Name</property> field you can enter any name you like. In the end press the <guibutton>OK</guibutton> button.
+ </para>
+ <figure>
+ <title>Add Update Site</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/getting_started/getting_started_4a.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ <listitem id="from_point">
+ <para>In the <property>Install</property> View select features to install, then click the <guibutton>Next</guibutton> button.</para>
+ <figure>
+ <title>JBoss Tools installation</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/getting_started/getting_started_4b.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ <listitem>
+ <para>And the system checks whether all necessary requirements and dependencies are installed on your Eclipse.</para>
+ <figure>
+ <title>Requirements and dependencies check</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/getting_started/getting_started_10.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>If some of the dependencies are missing an error message will appear and the installation process will be terminated.</para>
+ <note>
+ <title>Note:</title>
+ <para>
+ Sometimes when a user changes the list of plugins for download and clicks the <guibutton>Next</guibutton> button, after the required dependences have been checked, the list of missing dependencies from the previous attempt is showed. In this case completely closing the <emphasis>Install New Software</emphasis> dialog can help.
+ </para>
+ </note>
+ <para>
+ If JBoss Tools are already installed on your Eclipse and you are performing an update (and not installing new components) the following messages may appear in your <emphasis>Details</emphasis> section. Ignore them and press the <guibutton>Next</guibutton> button.
+ </para>
+ <figure>
+ <title>Possible messages</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/getting_started/getting_started_4c.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ <listitem>
+ <para>When you click the <guibutton>Finish</guibutton> button the Installation and/or Updating process will commence.</para>
+ </listitem>
+ <listitem>
+ <para>Once the installation is complete, restart Eclipse when prompted.</para>
+ <figure>
+ <title>Message dialog</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/getting_started/getting_started_4d.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ <listitem>
+ <para>
+ After fetching all the features and plugins for installation, you may be warned that your selection contains unsigned jars. This is normal, simply accept the warning and continue.
+ </para>
+ <figure>
+ <title>Warning Message</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/getting_started/getting_started_4e.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ </itemizedlist>
+
+ <note>
+ <title>Note:</title>
+ <para>
+ While installing JBoss Tools on GNU/Linux (64-bit) through the eclipse installation manager you may run into some problems which can interrupt your installation process. Please, read the <ulink url="http://www.jboss.org/community/wiki/ManualinstallationofJBossTools31xonEc...">Manual installation of JBoss Tools 3.1.x on Eclipse 3.5 on GNU/Linux (64-bit)</ulink> wiki article which provides you with the necessary steps to do it correct.
+ </para>
+ </note>
+ </section>
+ <section>
+ <title>Installation From Zip file</title>
+
+ <para>It is also possible to install JBoss Tools using the Eclipse P2 update manager and a common zip file which provides a single installer for all platforms.</para>
+ <para>You can download JBoss Tools in a zip file from one of the pages below:</para>
+ <itemizedlist id="zip_sites">
+ <listitem>
+ <para>Stable Releases: <ulink url="http://www.jboss.org/tools/download/stable.html">http://www.jboss.org/tools/download/stable.html</ulink>
+ </para>
+ </listitem>
+ <listitem>
+ <para> Development Updates: <ulink url="http://www.jboss.org/tools/download/dev.html">http://www.jboss.org/tools/download/dev.html</ulink>
+ </para>
+ </listitem>
+ <listitem>
+ <para> Nightly Builds: <ulink url="http://download.jboss.org/jbosstools/updates/nightly/">http://download.jboss.org/jbosstools/updates/nightly/</ulink>
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>When you downloaded Jboss Tools Zip please <emphasis>DO NOT UNZIP IT</emphasis> and follow the steps described below:</para>
+ <itemizedlist>
+ <listitem>
+ <para>When Eclipse is started, go to <menuchoice><guimenuitem>Help</guimenuitem>
+ <guimenuitem>Install New Software...</guimenuitem>
+ <guimenuitem>Add...</guimenuitem>
+ <guimenuitem>Archive...</guimenuitem>
+ </menuchoice>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Browse for the update site zip. In the <emphasis>Name</emphasis> field you can write any name you like. Then click the <guibutton>OK</guibutton> button.
+ </para>
+ <figure>
+ <title>Installation from a zip file</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/getting_started/getting_started_4f.png"/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ </listitem>
+ <listitem>
+ <para>
+ The remaining steps are the same as described in the section <link linkend="from_point">Installation From Update Site section</link>.
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ </section>
+
+ </section>
+ </section>
+</chapter>
Added: trunk/documentation/guides/GettingStartedGuide/en-US/introduction.xml
===================================================================
--- trunk/documentation/guides/GettingStartedGuide/en-US/introduction.xml (rev 0)
+++ trunk/documentation/guides/GettingStartedGuide/en-US/introduction.xml 2011-01-19 00:36:28 UTC (rev 28375)
@@ -0,0 +1,198 @@
+<chapter id="introduction">
+ <?dbhtml filename="getting_started.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>Eclipse</keyword>
+ <keyword>Java</keyword>
+ <keyword>JBoss</keyword>
+ </keywordset>
+ </chapterinfo>
+ <title>Introduction to JBoss Developer Studio</title>
+
+ <section id="intro1">
+ <title>What is JBDS?</title>
+ <para>
+ <property>JBoss Developer Studio</property> is a set of eclipse-based development tools that have been pre-configured for JBoss Enterprise Middleware Platforms and Red Hat Enterprise Linux. Developers are not required to use <property>JBoss Developer Studio</property> to develop on JBoss Enterprise Middleware and/or Red Hat Linux. But, many find these pre-configured tools offer significant time-savings and value, making them more pra JSPoductive reducing deployment times.
+ </para>
+ <para>
+ This guide covers the first steps required to get started with <property>JBoss Developer Studio</property>. You will learn how to install and configure the software necessary for your OS (currently Linux, Microsoft Windows or Mac OSX), including detailed information on how to install, configure and use JDK, JBDS and JBoss Tools.
+ </para>
+ </section>
+
+ <section>
+ <title>Key Features of JBoss Developer Studio and Requirements</title>
+ <para>The table below lists the main features of JBoss Developer Studio:</para>
+
+ <table>
+
+ <title>Key Functionality of JBoss Developer Studio</title>
+ <tgroup cols="2">
+
+ <colspec colnum="1" align="left" colwidth="2*"/>
+ <colspec colnum="2" colwidth="4*"/>
+
+ <thead>
+ <row>
+ <entry>Feature</entry>
+ <entry>Benefit</entry>
+
+ </row>
+ </thead>
+
+ <tbody>
+
+ <row>
+ <entry>
+ <para>JBoss Enterprise Application Platform</para>
+ </entry>
+ <entry>
+ <para>
+ JBoss Developer Studio includes and integrates JBoss Enterprise Application Platform, the same version of the middleware platform that Red Hat supports in production for 5 years.
+ </para>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <para>New Seam Tools</para>
+ </entry>
+ <entry>
+ <para>
+ JBoss Developer Studio includes brand new tools for Seam. They provide wizards for creating new Seam projects, validation tools, expression language code completion, testing tools, and wizards for generating entity objects.
+ </para>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <para>Visual Page Editor</para>
+ </entry>
+ <entry>
+ <para>
+ JBoss Developer Studio includes a Visual Page Editor for combined visual and source editing of Web pages. The Visual Page Editor even renders AJAX-enabled RichFaces components.
+ </para>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <para>AJAX Capabilities</para>
+ </entry>
+ <entry>
+ <para>
+ JBoss Developer Studio includes a Technology Preview of JBoss RichFaces. RichFaces provides nearly 70 skinnable components, including calendar, tree, dropdown menu, drag-and-drop components, and more. JBoss Developer Studio’s Visual Page Editor can render RichFaces components.
+ </para>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <para>JBoss Tools Palette</para>
+ </entry>
+ <entry>
+ <para>
+ The JBoss Tools Palette contains a developer’s project tag libraries and enables inserting tags into a JSP file with one click. The Tools Palette supports custom and 3rd party tags.
+ </para>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <para>JBoss jBPM Tools</para>
+ </entry>
+ <entry>
+ <para>JBoss Developer Studio includes jBPM tooling for defining Seam page flows.</para>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <para>Spring Tools</para>
+ </entry>
+ <entry>
+ <para>JBoss Developer Studio includes Spring IDE for developing Spring applications.</para>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <para>Struts Tools</para>
+ </entry>
+ <entry>
+ <para>JBoss Developer Studio includes Struts tools for Struts 1.x applications.</para>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <para>Optimized JBoss Application Server adapter</para>
+ </entry>
+ <entry>
+ <para>
+ JBoss Developer Studio’s advanced JBoss AS adapter includes features like incremental deployment for fast development and is pre-configured for the included JBoss Application server.
+ </para>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <para>Red Hat Enterprise Linux and RHN Access</para>
+ </entry>
+ <entry>
+ <para>
+ JBoss Developer Studio includes access to Red Hat Enterprise Linux, Linux development tools, and Red Hat Network for development purposes.
+ </para>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <para> Project Examples</para>
+ </entry>
+ <entry>
+ <para> Tooling for easy installation of Examples.</para>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <para>JBossWeb Service</para>
+ </entry>
+ <entry>
+ <para>
+ JBoss WS is a web service framework developed as a part of the JBoss Application Server. It implements the JAX-WS specification that defines a programming model and run-time architecture for implementing web services in Java, targeted at the Java Platform, Enterprise Edition 5 (Java EE 5).
+ </para>
+ </entry>
+ </row>
+
+ <row>
+ <entry>
+ <para>Usage reporting</para>
+ </entry>
+ <entry>
+ <para>
+ The usage plug-in anonymously gathers information on how you use the provided tools. This information is used to improve and shape the JBoss Developer Studio product to better cater to your needs. For more information refer to <xref linkend="Usage_Reporting"/>.
+ </para>
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+
+ <para>
+ <property>JBDS</property> requires JDK 5+ (JDK 6 in case of EAP 5.0). Also it's important that the JVM's architecture matches the particular <property>JBDS</property> build, i.e. if you're on a 64-bit system and use the 64-bit JVM, you need the 64-bit JBDS.
+ </para>
+
+ <para>
+ For the 32-bit version of JBDS use the 32-bit JVM or just use <literal>-vm</literal> flag to tell JBDS to use 32-bit java if the 64-bit one is found as the default.
+ </para>
+
+ <note>
+ <title>Note:</title>
+ <para>
+ On Linux system with 64-bit JVM the visual editor may fail to start. In this case you need the <literal>libstdc++.so.5</literal> library. See also the <link linkend="question_1">FAQ</link>.
+ </para>
+ </note>
+ </section>
+</chapter>
15 years, 2 months
JBoss Tools SVN: r28374 - branches/jbosstools-3.2.0.CR1/build/aggregate/site.
by jbosstools-commits@lists.jboss.org
Author: dgolovin
Date: 2011-01-18 19:17:47 -0500 (Tue, 18 Jan 2011)
New Revision: 28374
Modified:
branches/jbosstools-3.2.0.CR1/build/aggregate/site/build.xml
Log:
https://issues.jboss.org/browse/JBIDE-8029 Unable to install VPE on MacOSX 10.5 64bit
revert previous changes
Modified: branches/jbosstools-3.2.0.CR1/build/aggregate/site/build.xml
===================================================================
--- branches/jbosstools-3.2.0.CR1/build/aggregate/site/build.xml 2011-01-18 23:31:17 UTC (rev 28373)
+++ branches/jbosstools-3.2.0.CR1/build/aggregate/site/build.xml 2011-01-19 00:17:47 UTC (rev 28374)
@@ -207,9 +207,6 @@
<echo file="${update.site.source.dir}/content.xml" append="true"> </references>
</repository>
</echo>
-
- <xslt style="remove-uncategorized.xsl" in="${update.site.source.dir}/content.xml" out="${update.site.source.dir}/content.new.xml" />
- <move file="${update.site.source.dir}/content.new.xml" tofile="${update.site.source.dir}/content.xml" overwrite="true" />
<zip destfile="${update.site.source.dir}/content.jar" basedir="${update.site.source.dir}" includes="content.xml" />
<delete file="${update.site.source.dir}/content.xml" />
</then>
@@ -357,13 +354,4 @@
<delete dir="${aggegate.zips.dir}" quiet="true" />
</target>
- <target name="remove-uncategorized" >
- <!-- content.jar - full path to content.jar -->
- <property name="content.jar" value="/home/eskimo/Temp/content.jar" />
- <mkdir dir="${java.io.tmpdir}/content"/>
- <unzip src="${content.jar}" dest="${java.io.tmpdir}/content" />
-
- <xslt style="remove-uncategorized.xsl" in="${java.io.tmpdir}/content/content.xml" out="${java.io.tmpdir}/content/content.xml">
- </xslt>
- </target>
</project>
15 years, 2 months