May 2010 - jbosstools-commits - Jboss List Archives

JBoss Tools SVN: r22024 - trunk/documentation/guides/GettingStartedGuide/en-US.

by jbosstools-commits＠lists.jboss.org

Author: smukhina Date: 2010-05-11 15:36:49 -0400 (Tue, 11 May 2010) New Revision: 22024 Modified: trunk/documentation/guides/GettingStartedGuide/en-US/getting_started.xml Log: TOOLSDOC-30 - fixing links Modified: trunk/documentation/guides/GettingStartedGuide/en-US/getting_started.xml =================================================================== --- trunk/documentation/guides/GettingStartedGuide/en-US/getting_started.xml 2010-05-11 19:19:40 UTC (rev 22023) +++ trunk/documentation/guides/GettingStartedGuide/en-US/getting_started.xml 2010-05-11 19:36:49 UTC (rev 22024) @@ -1,917 +1,917 @@ -<?xml version="1.0" encoding="UTF-8"?> -<chapter id="getting_started" xreflabel="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> - - <section id="intro1"> - <title>What is JBDS?</title> - <para><property>JBoss Developer Studio</property> is a set of eclipse-based development tools that - are 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 productive and speeding time to deployment.</para> - <para>This guide covers the first steps to get started working with <property>JBoss Developer - Studio</property>. You will learn how to install and configure necessary software for your OS - (currently Linux, Microsoft Windows or Mac OSX).</para> - <para>Thus this guide will provide you with detailed info on how to start JDK, JBDS and JBoss - Tools.</para> - </section> - -<section> - <title>Key Features of JBoss Developer Studio and Requirements</title> - <para>For a start, we propose you to look through the table of 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 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> - </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> - - <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> - <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> - - <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/pre-configured versions of Eclipse, - WTP, JBossEAP, Seam, and SpringIDE. Thus, to start perform the next steps:</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>Then run in console:</para> - <programlisting role="JAVA"><![CDATA[java -jar jbdevstudio-eap-linux-gtk-3.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 Java VM</para> - </listitem> - </itemizedlist> - - <figure> - <title>Select Java VM</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/getting_started/getting_started_2.png"/> - </imageobject> - </mediaobject> - </figure> - - <tip> - <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> - </tip> - - <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 3.0 comes integrated with JBoss EAP 5.0 that requires JDK 6.0 to run - and "gij" isn't available on every platform.</para> - </note> - - <itemizedlist> - <listitem> - <para>Installation process includes <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 3.0.0.GA comes integrated with JBoss EAP 5.0 - 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 <emphasis><property>Find</property></emphasis> button: click <emphasis><property>Find</property></emphasis>, select a folder where search of available JBoss Application Servers should be started and click on <emphasis><property>Ok</property></emphasis>: </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 information specified: Name, Type, Version and Location. - </para></listitem> - </itemizedlist> - - <itemizedlist> - <listitem><para>You can also add servers one by one using the - <emphasis><property>Add</property></emphasis> 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 <emphasis><property>Browse</property></emphasis> 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>Click on <emphasis><property>Ok</property></emphasis>. The server is added to the list with the details on its type, version and location.</para> - - - - <para>The <emphasis><property>Remove</property></emphasis> button will the remove the selected server from the list. If necessary, you can edit the server details clicking on the <emphasis><property>Edit</property></emphasis> button:</para> - - <figure> - <title>Edit Server</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/getting_started/getting_started_3_4.png"/> - </imageobject> - </mediaobject> - </figure> - <para/> - -  - - <itemizedlist> - <listitem> - <para>Click <emphasis><property>Next</property></emphasis>. Check your installation paths and see the components to install. If you'd like to change - something, press the <emphasis> - <property>Previous</property> - </emphasis> button. Click <emphasis> - <property>Next</property> - </emphasis> 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 uncovers the points on the differences between <property>JBoss Developer - Studio</property> and <property>JBoss Tools</property> and provides the steps on <property>JBoss - Tools</property> installation as well.</para> - - <section id="WhatDifferenceBetweenJBDSAndJBossTools"> - <title>What is the difference?</title> - - <para><property>JBoss Tools</property> is what went into our <property>JBoss Developer - Studio</property> which comes as 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>Here, let's consider 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 will make it into <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> - </itemizedlist> - - <para>To install the JBoss Tools plugins for Eclipse, you need the following:</para> - - <itemizedlist> - <listitem> - <para>Get 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.1.0.GA) targets at Eclipse 3.5.2 Galileo JEE Bundle which is available from <ulink url="http://www.eclipse.org/downloads/">eclipse.org</ulink>.</para> - - <tip> - <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> - </tip> - - <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://labs.jboss.com/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/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/updating process using some of Jboss - update sites <emphasis>No repository found containing...</emphasis> error - can appear.It is a Eclipse P2 bug.To work around it try:1.Restart your Eclipse. 2. - Add the update site again. 3. - Do the update again.</para> - </note> - <para>To install/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.1.0.GA Eclipse 3.5.2 Galileo 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>Help->Software Updates... ->Available Software->Manage Sites...->Add...<emphasis>(Eclipse 3.4)</emphasis></para></listitem> - <listitem><para>Help->Install New Software->Add..<emphasis>(Eclipse 3.5)</emphasis></para></listitem> - </itemizedlist> - </para></listitem> - <listitem><para>After clicking <emphasis>Add</emphasis> button <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 <property>Name</property> you can write any name you like. - In the end press the <property>Ok</property> 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 <emphasis>Next</emphasis>.</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 them 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 - <emphasis>Next</emphasis>, after required dependences check, - the list of missing dependencies of the previous attempt is showed. - In this case the completely close of the <emphasis>Install New Software</emphasis> dialog can help.</para> - </note> - <para>If Jboss Tools are already installed on your Eclipse and you are doing updating but not - installation the following messages will appear in your <emphasis>Details</emphasis> section. - Ignore them and press <emphasis>Next.</emphasis></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 Finish the prosses of Installation/Updating starts up. </para></listitem> - <listitem><para>Install. Restart 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 prompted 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>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 <property>Help -> Install New Software... -> Add... -> Archive...</property></para></listitem> - <listitem><para>Browse for the update site zip.In the <emphasis>Name</emphasis> field you can write any name you like. - In the end press <property>Ok</property> 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>All the other steps are the same as it was described in the <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 description of perspectives that JBDS offers for more productive - development</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>Start work with <property>JBoss Developer Studio</property> by clicking on <emphasis> - <property>Workbench</property> - </emphasis> button or simply close the Welcome page.</para> - - </section> - - <section id="Upgrading"> - <?dbhtml filename="Upgrading.html"?> - <title>Upgrading</title> - <para>As opposed to upgrading your JBDS from 2.0 to 2.1 using the update site, - to upgrade your JBDS from 2.1 to 3.0 you have to uninstall your 2.1 version and install the new one - because of some platform change.</para> - - </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 - Uninstaller</para> - </listitem> - </itemizedlist> - </section> - - <section id="Support"> - <?dbhtml filename="Support.html"?> - <title>Support</title> - <para>If you have comments or questions, you can discuss them at our <ulink url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=258">JBoss - Developer Studio Forum</ulink>.</para> - <para>When writing to the forum for questions, 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 necessary 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> - -</chapter> +<?xml version="1.0" encoding="UTF-8"?> +<chapter id="getting_started" xreflabel="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> + + <section id="intro1"> + <title>What is JBDS?</title> + <para><property>JBoss Developer Studio</property> is a set of eclipse-based development tools that + are 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 productive and speeding time to deployment.</para> + <para>This guide covers the first steps to get started working with <property>JBoss Developer + Studio</property>. You will learn how to install and configure necessary software for your OS + (currently Linux, Microsoft Windows or Mac OSX).</para> + <para>Thus this guide will provide you with detailed info on how to start JDK, JBDS and JBoss + Tools.</para> + </section> + +<section> + <title>Key Features of JBoss Developer Studio and Requirements</title> + <para>For a start, we propose you to look through the table of 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 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> + </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> + + <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> + <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> + + <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/pre-configured versions of Eclipse, + WTP, JBossEAP, Seam, and SpringIDE. Thus, to start perform the next steps:</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>Then run in console:</para> + <programlisting role="JAVA"><![CDATA[java -jar jbdevstudio-eap-linux-gtk-3.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 Java VM</para> + </listitem> + </itemizedlist> + + <figure> + <title>Select Java VM</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/getting_started/getting_started_2.png"/> + </imageobject> + </mediaobject> + </figure> + + <tip> + <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> + </tip> + + <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 3.0 comes integrated with JBoss EAP 5.0 that requires JDK 6.0 to run + and "gij" isn't available on every platform.</para> + </note> + + <itemizedlist> + <listitem> + <para>Installation process includes <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 3.0.0.GA comes integrated with JBoss EAP 5.0 + 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 <emphasis><property>Find</property></emphasis> button: click <emphasis><property>Find</property></emphasis>, select a folder where search of available JBoss Application Servers should be started and click on <emphasis><property>Ok</property></emphasis>: </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 information specified: Name, Type, Version and Location. + </para></listitem> + </itemizedlist> + + <itemizedlist> + <listitem><para>You can also add servers one by one using the + <emphasis><property>Add</property></emphasis> 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 <emphasis><property>Browse</property></emphasis> 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>Click on <emphasis><property>Ok</property></emphasis>. The server is added to the list with the details on its type, version and location.</para> + + + + <para>The <emphasis><property>Remove</property></emphasis> button will the remove the selected server from the list. If necessary, you can edit the server details clicking on the <emphasis><property>Edit</property></emphasis> button:</para> + + <figure> + <title>Edit Server</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/getting_started/getting_started_3_4.png"/> + </imageobject> + </mediaobject> + </figure> + <para/> + +  + + <itemizedlist> + <listitem> + <para>Click <emphasis><property>Next</property></emphasis>. Check your installation paths and see the components to install. If you'd like to change + something, press the <emphasis> + <property>Previous</property> + </emphasis> button. Click <emphasis> + <property>Next</property> + </emphasis> 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 uncovers the points on the differences between <property>JBoss Developer + Studio</property> and <property>JBoss Tools</property> and provides the steps on <property>JBoss + Tools</property> installation as well.</para> + + <section id="WhatDifferenceBetweenJBDSAndJBossTools"> + <title>What is the difference?</title> + + <para><property>JBoss Tools</property> is what went into our <property>JBoss Developer + Studio</property> which comes as 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>Here, let's consider 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 will make it into <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> + </itemizedlist> + + <para>To install the JBoss Tools plugins for Eclipse, you need the following:</para> + + <itemizedlist> + <listitem> + <para>Get 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.1.0.GA) targets at Eclipse 3.5.2 Galileo JEE Bundle which is available from <ulink url="http://www.eclipse.org/downloads/">eclipse.org</ulink>.</para> + + <tip> + <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> + </tip> + + <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/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/updating process using some of Jboss + update sites <emphasis>No repository found containing...</emphasis> error + can appear.It is a Eclipse P2 bug.To work around it try:1.Restart your Eclipse. 2. + Add the update site again. 3. + Do the update again.</para> + </note> + <para>To install/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.1.0.GA Eclipse 3.5.2 Galileo 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>Help->Software Updates... ->Available Software->Manage Sites...->Add...<emphasis>(Eclipse 3.4)</emphasis></para></listitem> + <listitem><para>Help->Install New Software->Add..<emphasis>(Eclipse 3.5)</emphasis></para></listitem> + </itemizedlist> + </para></listitem> + <listitem><para>After clicking <emphasis>Add</emphasis> button <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 <property>Name</property> you can write any name you like. + In the end press the <property>Ok</property> 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 <emphasis>Next</emphasis>.</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 them 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 + <emphasis>Next</emphasis>, after required dependences check, + the list of missing dependencies of the previous attempt is showed. + In this case the completely close of the <emphasis>Install New Software</emphasis> dialog can help.</para> + </note> + <para>If Jboss Tools are already installed on your Eclipse and you are doing updating but not + installation the following messages will appear in your <emphasis>Details</emphasis> section. + Ignore them and press <emphasis>Next.</emphasis></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 Finish the prosses of Installation/Updating starts up. </para></listitem> + <listitem><para>Install. Restart 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 prompted 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>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 <property>Help -> Install New Software... -> Add... -> Archive...</property></para></listitem> + <listitem><para>Browse for the update site zip.In the <emphasis>Name</emphasis> field you can write any name you like. + In the end press <property>Ok</property> 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>All the other steps are the same as it was described in the <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 description of perspectives that JBDS offers for more productive + development</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>Start work with <property>JBoss Developer Studio</property> by clicking on <emphasis> + <property>Workbench</property> + </emphasis> button or simply close the Welcome page.</para> + + </section> + + <section id="Upgrading"> + <?dbhtml filename="Upgrading.html"?> + <title>Upgrading</title> + <para>As opposed to upgrading your JBDS from 2.0 to 2.1 using the update site, + to upgrade your JBDS from 2.1 to 3.0 you have to uninstall your 2.1 version and install the new one + because of some platform change.</para> + + </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 + Uninstaller</para> + </listitem> + </itemizedlist> + </section> + + <section id="Support"> + <?dbhtml filename="Support.html"?> + <title>Support</title> + <para>If you have comments or questions, you can discuss them at our <ulink url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=258">JBoss + Developer Studio Forum</ulink>.</para> + <para>When writing to the forum for questions, 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 necessary 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> + +</chapter> \ No newline at end of file

15 years, 11 months

1
0
0 / 0

JBoss Tools SVN: r22023 - in branches/modular_build/drools: features and 3 other directories.

by jbosstools-commits＠lists.jboss.org

Author: nickboldt Date: 2010-05-11 15:19:40 -0400 (Tue, 11 May 2010) New Revision: 22023 Added: branches/modular_build/drools/features/ branches/modular_build/drools/features/org.drools.eclipse.feature/ branches/modular_build/drools/features/org.drools.eclipse.feature/pom.xml branches/modular_build/drools/features/org.drools.eclipse.task.feature/ branches/modular_build/drools/features/org.drools.eclipse.task.feature/pom.xml branches/modular_build/drools/features/org.guvnor.tools.feature/ branches/modular_build/drools/features/org.guvnor.tools.feature/pom.xml branches/modular_build/drools/features/pom.xml Log: add generated pom.xml for drools build Added: branches/modular_build/drools/features/org.drools.eclipse.feature/pom.xml =================================================================== --- branches/modular_build/drools/features/org.drools.eclipse.feature/pom.xml (rev 0) +++ branches/modular_build/drools/features/org.drools.eclipse.feature/pom.xml 2010-05-11 19:19:40 UTC (rev 22023) @@ -0,0 +1,14 @@ +<project +xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> + <modelVersion>4.0.0</modelVersion> + <parent> + <relativePath>../../../parent-pom.xml</relativePath> + <groupId>org.jboss.tools</groupId> + <artifactId>org.jboss.tools.parent.pom</artifactId> + <version>0.0.1-SNAPSHOT</version> + </parent> + <groupId>org.jboss.tools</groupId> + <artifactId>org.drools.eclipse.feature</artifactId> + <version>5.1.0-SNAPSHOT</version> + <packaging>eclipse-feature</packaging> +</project> Property changes on: branches/modular_build/drools/features/org.drools.eclipse.feature/pom.xml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: branches/modular_build/drools/features/org.drools.eclipse.task.feature/pom.xml =================================================================== --- branches/modular_build/drools/features/org.drools.eclipse.task.feature/pom.xml (rev 0) +++ branches/modular_build/drools/features/org.drools.eclipse.task.feature/pom.xml 2010-05-11 19:19:40 UTC (rev 22023) @@ -0,0 +1,14 @@ +<project +xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> + <modelVersion>4.0.0</modelVersion> + <parent> + <relativePath>../../../parent-pom.xml</relativePath> + <groupId>org.jboss.tools</groupId> + <artifactId>org.jboss.tools.parent.pom</artifactId> + <version>0.0.1-SNAPSHOT</version> + </parent> + <groupId>org.jboss.tools</groupId> + <artifactId>org.drools.eclipse.task.feature</artifactId> + <version>5.1.0-SNAPSHOT</version> + <packaging>eclipse-feature</packaging> +</project> Property changes on: branches/modular_build/drools/features/org.drools.eclipse.task.feature/pom.xml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: branches/modular_build/drools/features/org.guvnor.tools.feature/pom.xml =================================================================== --- branches/modular_build/drools/features/org.guvnor.tools.feature/pom.xml (rev 0) +++ branches/modular_build/drools/features/org.guvnor.tools.feature/pom.xml 2010-05-11 19:19:40 UTC (rev 22023) @@ -0,0 +1,14 @@ +<project +xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> + <modelVersion>4.0.0</modelVersion> + <parent> + <relativePath>../../../parent-pom.xml</relativePath> + <groupId>org.jboss.tools</groupId> + <artifactId>org.jboss.tools.parent.pom</artifactId> + <version>0.0.1-SNAPSHOT</version> + </parent> + <groupId>org.jboss.tools</groupId> + <artifactId>org.guvnor.tools.feature</artifactId> + <version>5.1.0-SNAPSHOT</version> + <packaging>eclipse-feature</packaging> +</project> Property changes on: branches/modular_build/drools/features/org.guvnor.tools.feature/pom.xml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: branches/modular_build/drools/features/pom.xml =================================================================== --- branches/modular_build/drools/features/pom.xml (rev 0) +++ branches/modular_build/drools/features/pom.xml 2010-05-11 19:19:40 UTC (rev 22023) @@ -0,0 +1,20 @@ +<project +xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> + <modelVersion>4.0.0</modelVersion> + <parent> + <relativePath>../../parent-pom.xml</relativePath> + <groupId>org.jboss.tools</groupId> + <artifactId>org.jboss.tools.parent.pom</artifactId> + <version>0.0.1-SNAPSHOT</version> + </parent> + <groupId>org.jboss.tools</groupId> + <artifactId>drools.features</artifactId> + <version>0.0.1-SNAPSHOT</version> + <packaging>pom</packaging> + <modules> + <module>org.drools.eclipse.feature</module> + <module>org.drools.eclipse.task.feature</module> + <module>org.guvnor.tools.feature</module> + </modules> +</project> + \ No newline at end of file Property changes on: branches/modular_build/drools/features/pom.xml ___________________________________________________________________ Name: svn:mime-type + text/plain

15 years, 11 months

1
0
0 / 0

JBoss Tools SVN: r22022 - in branches/modular_build/drools/plugins: org.drools.eclipse and 3 other directories.

by jbosstools-commits＠lists.jboss.org

Author: nickboldt Date: 2010-05-11 15:15:28 -0400 (Tue, 11 May 2010) New Revision: 22022 Added: branches/modular_build/drools/plugins/org.drools.eclipse.task/ branches/modular_build/drools/plugins/org.drools.eclipse.task/pom.xml branches/modular_build/drools/plugins/org.drools.eclipse/ branches/modular_build/drools/plugins/org.drools.eclipse/pom.xml branches/modular_build/drools/plugins/org.eclipse.webdav/ branches/modular_build/drools/plugins/org.eclipse.webdav/pom.xml branches/modular_build/drools/plugins/org.guvnor.tools/ branches/modular_build/drools/plugins/org.guvnor.tools/pom.xml branches/modular_build/drools/plugins/pom.xml Log: add generated pom.xml for drools build Added: branches/modular_build/drools/plugins/org.drools.eclipse/pom.xml =================================================================== --- branches/modular_build/drools/plugins/org.drools.eclipse/pom.xml (rev 0) +++ branches/modular_build/drools/plugins/org.drools.eclipse/pom.xml 2010-05-11 19:15:28 UTC (rev 22022) @@ -0,0 +1,14 @@ +<project +xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> + <modelVersion>4.0.0</modelVersion> + <parent> + <relativePath>../../../parent-pom.xml</relativePath> + <groupId>org.jboss.tools</groupId> + <artifactId>org.jboss.tools.parent.pom</artifactId> + <version>0.0.1-SNAPSHOT</version> + </parent> + <groupId>org.jboss.tools</groupId> + <artifactId>org.drools.eclipse</artifactId> + <version>5.1.0-SNAPSHOT</version> + <packaging>eclipse-plugin</packaging> +</project> Property changes on: branches/modular_build/drools/plugins/org.drools.eclipse/pom.xml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: branches/modular_build/drools/plugins/org.drools.eclipse.task/pom.xml =================================================================== --- branches/modular_build/drools/plugins/org.drools.eclipse.task/pom.xml (rev 0) +++ branches/modular_build/drools/plugins/org.drools.eclipse.task/pom.xml 2010-05-11 19:15:28 UTC (rev 22022) @@ -0,0 +1,14 @@ +<project +xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> + <modelVersion>4.0.0</modelVersion> + <parent> + <relativePath>../../../parent-pom.xml</relativePath> + <groupId>org.jboss.tools</groupId> + <artifactId>org.jboss.tools.parent.pom</artifactId> + <version>0.0.1-SNAPSHOT</version> + </parent> + <groupId>org.jboss.tools</groupId> + <artifactId>org.drools.eclipse.task</artifactId> + <version>5.1.0-SNAPSHOT</version> + <packaging>eclipse-plugin</packaging> +</project> Property changes on: branches/modular_build/drools/plugins/org.drools.eclipse.task/pom.xml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: branches/modular_build/drools/plugins/org.eclipse.webdav/pom.xml =================================================================== --- branches/modular_build/drools/plugins/org.eclipse.webdav/pom.xml (rev 0) +++ branches/modular_build/drools/plugins/org.eclipse.webdav/pom.xml 2010-05-11 19:15:28 UTC (rev 22022) @@ -0,0 +1,14 @@ +<project +xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> + <modelVersion>4.0.0</modelVersion> + <parent> + <relativePath>../../../parent-pom.xml</relativePath> + <groupId>org.jboss.tools</groupId> + <artifactId>org.jboss.tools.parent.pom</artifactId> + <version>0.0.1-SNAPSHOT</version> + </parent> + <groupId>org.jboss.tools</groupId> + <artifactId>org.eclipse.webdav</artifactId> + <version>3.0.101</version> + <packaging>eclipse-plugin</packaging> +</project> Property changes on: branches/modular_build/drools/plugins/org.eclipse.webdav/pom.xml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: branches/modular_build/drools/plugins/org.guvnor.tools/pom.xml =================================================================== --- branches/modular_build/drools/plugins/org.guvnor.tools/pom.xml (rev 0) +++ branches/modular_build/drools/plugins/org.guvnor.tools/pom.xml 2010-05-11 19:15:28 UTC (rev 22022) @@ -0,0 +1,14 @@ +<project +xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> + <modelVersion>4.0.0</modelVersion> + <parent> + <relativePath>../../../parent-pom.xml</relativePath> + <groupId>org.jboss.tools</groupId> + <artifactId>org.jboss.tools.parent.pom</artifactId> + <version>0.0.1-SNAPSHOT</version> + </parent> + <groupId>org.jboss.tools</groupId> + <artifactId>org.guvnor.tools</artifactId> + <version>5.1.0-SNAPSHOT</version> + <packaging>eclipse-plugin</packaging> +</project> Property changes on: branches/modular_build/drools/plugins/org.guvnor.tools/pom.xml ___________________________________________________________________ Name: svn:mime-type + text/plain Added: branches/modular_build/drools/plugins/pom.xml =================================================================== --- branches/modular_build/drools/plugins/pom.xml (rev 0) +++ branches/modular_build/drools/plugins/pom.xml 2010-05-11 19:15:28 UTC (rev 22022) @@ -0,0 +1,22 @@ +<project +xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> + <modelVersion>4.0.0</modelVersion> + <parent> + <relativePath>../../parent-pom.xml</relativePath> + <groupId>org.jboss.tools</groupId> + <artifactId>org.jboss.tools.parent.pom</artifactId> + <version>0.0.1-SNAPSHOT</version> + </parent> + <groupId>org.jboss.tools</groupId> + <artifactId>drools.plugins</artifactId> + <version>0.0.1-SNAPSHOT</version> + <packaging>pom</packaging> + <modules> + <module>org.drools.eclipse</module> + <module>org.drools.eclipse.task</module> + <module>org.eclipse.webdav</module> + <module>org.guvnor.tools</module> + <module>org.jboss.tools.flow.ruleflow</module> + </modules> +</project> + \ No newline at end of file Property changes on: branches/modular_build/drools/plugins/pom.xml ___________________________________________________________________ Name: svn:mime-type + text/plain

15 years, 11 months

1
0
0 / 0

JBoss Tools SVN: r22021 - branches/modular_build/drools.

by jbosstools-commits＠lists.jboss.org

Author: nickboldt Date: 2010-05-11 15:13:03 -0400 (Tue, 11 May 2010) New Revision: 22021 Modified: branches/modular_build/drools/ Log: svn:ignore drools-5.1.0.SNAPSHOT-eclipse-all.zip Property changes on: branches/modular_build/drools ___________________________________________________________________ Name: svn:ignore + drools-5.1.0.SNAPSHOT-eclipse-all.zip

15 years, 11 months

1
0
0 / 0

JBoss Tools SVN: r22020 - branches/modular_build/build.

by jbosstools-commits＠lists.jboss.org

Author: nickboldt Date: 2010-05-11 15:09:39 -0400 (Tue, 11 May 2010) New Revision: 22020 Modified: branches/modular_build/build/build.xml Log: fix bootstrapping for drools build; add constraint for custom build.xml: run only if pom.xml does not call custom build.xml directly Modified: branches/modular_build/build/build.xml =================================================================== --- branches/modular_build/build/build.xml 2010-05-11 19:06:24 UTC (rev 22019) +++ branches/modular_build/build/build.xml 2010-05-11 19:09:39 UTC (rev 22020) @@ -574,8 +574,17 @@ </else> </if>  + <loadfile property="@{COMPONENT}.pom.xml" srcfile="${WORKINGDIR}/(a){COMPONENT}/pom.xml" /> <if> - <available file="${WORKINGDIR}/(a){COMPONENT}/build.xml" type="file" /> + <and> +  + <not> + <contains string="${(a){COMPONENT}.pom.xml}" + substring="<ant antfile="build.xml" />" + /> + </not> + <available file="${WORKINGDIR}/(a){COMPONENT}/build.xml" type="file" /> + </and> <then> <echo>Run custom @{COMPONENT}/build.xml</echo> <ant antfile="${WORKINGDIR}/(a){COMPONENT}/build.xml">

15 years, 11 months

1
0
0 / 0

JBoss Tools SVN: r22019 - branches/modular_build/build.

by jbosstools-commits＠lists.jboss.org

Author: nickboldt Date: 2010-05-11 15:06:24 -0400 (Tue, 11 May 2010) New Revision: 22019 Modified: branches/modular_build/build/build.xml Log: fix bootstrapping for drools build Modified: branches/modular_build/build/build.xml =================================================================== --- branches/modular_build/build/build.xml 2010-05-11 19:06:11 UTC (rev 22018) +++ branches/modular_build/build/build.xml 2010-05-11 19:06:24 UTC (rev 22019) @@ -322,7 +322,7 @@ <istrue value="${svnant.enabled}" /> <then>  - <delete dir="${WORKINGDIR}/@{component}/site" includeemptydirs="true" quiet="true"/> + <delete dir="${WORKINGDIR}/@{component}/site" includeemptydirs="true" quiet="true" /> <svn javahl="false" svnkit="true" failonerror="false"> <revert recurse="${svn.recurse}" dir="@{component}" /> </svn> @@ -531,7 +531,7 @@ </if> </then> <else> - <antcallback target="get.all.components" return="COMPONENTS.to.build"/> + <antcallback target="get.all.components" return="COMPONENTS.to.build" /> </else> </if> </target> @@ -1178,6 +1178,27 @@ </for> </target> +  + <target name="renameFeatures"> + <echo>${WORKINGDIR}/${COMPONENT}/features</echo> + <for param="artifactJar"> + <path> + <dirset dir="${WORKINGDIR}/${COMPONENT}/features" includes="*feature_*" /> + </path> + <sequential> + <antcallback target="get.artifact.id" return="artifact.id"> + <property name="artifactJar" value="@{artifactJar}" /> + <property name="regexp.path" value=".+/features/([^/]+feature)_\d+.+" /> + </antcallback> + <move file="@{artifactJar}" + tofile="${WORKINGDIR}/${COMPONENT}/features/${artifact.id}" + overwrite="true" + /> + <var name="artifact.id" unset="true" /> + </sequential> + </for> + </target> +  <target name="snapshot2qualifier"> <property name="COMPONENT" value="" /> @@ -1204,8 +1225,8 @@ <target name="genBuildProperties"> <for param="artifactDir"> <path> - <dirset dir="${WORKINGDIR}/${COMPONENT}/features/" /> - <dirset dir="${WORKINGDIR}/${COMPONENT}/plugins/" /> + <dirset dir="${WORKINGDIR}/${COMPONENT}/features/" excludes="." includes="*" /> + <dirset dir="${WORKINGDIR}/${COMPONENT}/plugins/" excludes="." includes="*" /> </path> <sequential> <if>

15 years, 11 months

1
0
0 / 0

JBoss Tools SVN: r22018 - branches/modular_build/drools.

by jbosstools-commits＠lists.jboss.org

Author: nickboldt Date: 2010-05-11 15:06:11 -0400 (Tue, 11 May 2010) New Revision: 22018 Modified: branches/modular_build/drools/build.xml Log: fix bootstrapping for drools build Modified: branches/modular_build/drools/build.xml =================================================================== --- branches/modular_build/drools/build.xml 2010-05-11 18:44:17 UTC (rev 22017) +++ branches/modular_build/drools/build.xml 2010-05-11 19:06:11 UTC (rev 22018) @@ -31,11 +31,21 @@ usetimestamp="true" /> <unzip src="${WORKINGDIR}/${COMPONENT}/${drools.zip}" dest="${WORKINGDIR}/${COMPONENT}" overwrite="true" /> +  <ant antfile="${build.xml}" target="unjarPlugins"> <property name="COMPONENT" value="${COMPONENT}" /> </ant> + <delete dir="${WORKINGDIR}/${COMPONENT}" quiet="true" includes=" + LICENSE-ASL-2.0.txt, README_DEPENDENCIES.txt, + plugins/*.jar + "/> + + <ant antfile="${build.xml}" target="renameFeatures"> + <property name="COMPONENT" value="${COMPONENT}" /> + </ant> + <ant antfile="${build.xml}" target="snapshot2qualifier"> <property name="COMPONENT" value="${COMPONENT}" /> </ant> @@ -43,6 +53,7 @@ <ant antfile="${build.xml}" target="genBuildProperties"> <property name="COMPONENT" value="${COMPONENT}" /> </ant> + </target> <target name="init">

15 years, 11 months

1
0
0 / 0

JBoss Tools SVN: r22017 - in branches/modular_build/drools: plugins/org.jboss.tools.flow.ruleflow and 1 other directory.

by jbosstools-commits＠lists.jboss.org

Author: nickboldt Date: 2010-05-11 14:44:17 -0400 (Tue, 11 May 2010) New Revision: 22017 Added: branches/modular_build/drools/plugins/org.jboss.tools.flow.ruleflow/pom.xml branches/modular_build/drools/pom.xml Modified: branches/modular_build/drools/build.xml Log: make pom run build.xml instead of build.xml being run before pom Modified: branches/modular_build/drools/build.xml =================================================================== --- branches/modular_build/drools/build.xml 2010-05-11 18:37:27 UTC (rev 22016) +++ branches/modular_build/drools/build.xml 2010-05-11 18:44:17 UTC (rev 22017) @@ -1,8 +1,27 @@ <project default="custom.build" name="jbosstools drools build.xml"> -  +  + <property name="COMPONENT" value="drools" /> <property name="drools.zip" value="drools-5.1.0.SNAPSHOT-eclipse-all.zip" /> +  + <condition property="WORKINGDIR" value="/home/hudson/static_build_env/jbds/tools/sources/"> + <available file="/home/hudson/static_build_env/jbds" type="dir" /> + </condition> + <condition property="WORKINGDIR" value="${basedir}/../build" else="${basedir}/../"> + <available file="${basedir}/../build/${COMPONENT}" type="dir" /> + </condition> + + <mkdir dir="${WORKINGDIR}" /> + <echo level="info">WORKINGDIR = ${WORKINGDIR}</echo> + + <condition property="build.xml" value="/home/hudson/static_build_env/jbds/tools/sources"> + <available file="/home/hudson/static_build_env/jbds/tools/sources/build/build.xml" type="file" /> + </condition> + <condition property="build.xml" value="${basedir}/../build/build.xml" else="${basedir}/../build.xml"> + <available file="${basedir}/../build/build.xml" type="file" /> + </condition> + <target name="custom.build" description="fetch latest drools from their Hudson build + selectively unpack it" depends="init" @@ -12,7 +31,7 @@ usetimestamp="true" /> <unzip src="${WORKINGDIR}/${COMPONENT}/${drools.zip}" dest="${WORKINGDIR}/${COMPONENT}" overwrite="true" /> - + <ant antfile="${build.xml}" target="unjarPlugins"> <property name="COMPONENT" value="${COMPONENT}" /> </ant> @@ -27,8 +46,12 @@ </target> <target name="init"> - <property name="build.xml" value="${WORKINGDIR}/build.xml" /> <ant antfile="${build.xml}" target="init" /> + <taskdef resource="net/sf/antcontrib/antlib.xml"> + <classpath> + <pathelement location="${COMMON_TOOLS}/ant-contrib.jar" /> + </classpath> + </taskdef> </target> </project> Added: branches/modular_build/drools/plugins/org.jboss.tools.flow.ruleflow/pom.xml =================================================================== --- branches/modular_build/drools/plugins/org.jboss.tools.flow.ruleflow/pom.xml (rev 0) +++ branches/modular_build/drools/plugins/org.jboss.tools.flow.ruleflow/pom.xml 2010-05-11 18:44:17 UTC (rev 22017) @@ -0,0 +1,14 @@ +<project +xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> + <modelVersion>4.0.0</modelVersion> + <parent> + <relativePath>../../../parent-pom.xml</relativePath> + <groupId>org.jboss.tools</groupId> + <artifactId>org.jboss.tools.parent.pom</artifactId> + <version>0.0.1-SNAPSHOT</version> + </parent> + <groupId>org.jboss.tools</groupId> + <artifactId>org.jboss.tools.flow.ruleflow</artifactId> + <version>1.0.0-SNAPSHOT</version> + <packaging>eclipse-plugin</packaging> +</project> Added: branches/modular_build/drools/pom.xml =================================================================== --- branches/modular_build/drools/pom.xml (rev 0) +++ branches/modular_build/drools/pom.xml 2010-05-11 18:44:17 UTC (rev 22017) @@ -0,0 +1,68 @@ +<project + xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" + xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> + <modelVersion>4.0.0</modelVersion> + <parent> + <relativePath>../parent-pom.xml</relativePath> + <groupId>org.jboss.tools</groupId> + <artifactId>org.jboss.tools.parent.pom</artifactId> + <version>0.0.1-SNAPSHOT</version> + </parent> + <groupId>org.jboss.tools</groupId> + <artifactId>drools</artifactId> + <version>0.0.1-SNAPSHOT</version> + <packaging>pom</packaging> + <modules> + <module>plugins</module> + <module>features</module> + </modules> + + <build> + <plugins> + + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-antrun-plugin</artifactId> + <version>1.3</version> + <executions> + <execution> + <id>compile</id> + <phase>compile</phase> + <configuration> + <tasks> + <ant antfile="build.xml" /> + </tasks> + </configuration> + <goals> + <goal>run</goal> + </goals> + </execution> + </executions> + <dependencies> + <dependency> + <groupId>commons-net</groupId> + <artifactId>commons-net</artifactId> + <version>1.4.1</version> + </dependency> + <dependency> + <groupId>org.apache.ant</groupId> + <artifactId>ant-commons-net</artifactId> + <version>1.7.1</version> + </dependency> + <dependency> + <groupId>org.apache.ant</groupId> + <artifactId>ant-apache-regexp</artifactId> + <version>1.7.1</version> + </dependency> + <dependency> + <groupId>ant-contrib</groupId> + <artifactId>ant-contrib</artifactId> + <version>1.0b3</version> + </dependency> + </dependencies> + + </plugin> + </plugins> + </build> +</project> +

15 years, 11 months

1
0
0 / 0

JBoss Tools SVN: r22016 - in trunk: drools/tests/org.jboss.tools.drools.ui.bot.test/src/org/jboss/tools/drools/ui/bot/test/smoke and 2 other directories.

by jbosstools-commits＠lists.jboss.org

Author: vpakan(a)redhat.com Date: 2010-05-11 14:37:27 -0400 (Tue, 11 May 2010) New Revision: 22016 Added: trunk/drools/tests/org.jboss.tools.drools.ui.bot.test/src/org/jboss/tools/drools/ui/bot/test/smoke/OpenDroolsPerspective.java Modified: trunk/drools/tests/org.jboss.tools.drools.ui.bot.test/src/org/jboss/tools/drools/ui/bot/test/DroolsAllBotTests.java trunk/drools/tests/org.jboss.tools.drools.ui.bot.test/src/org/jboss/tools/drools/ui/bot/test/smoke/RuleFlowTest.java trunk/jst/tests/org.jboss.tools.ui.bot.ext/src/org/jboss/tools/ui/bot/ext/SWTEclipseExt.java trunk/jst/tests/org.jboss.tools.ui.bot.ext/src/org/jboss/tools/ui/bot/ext/types/IDELabel.java trunk/jst/tests/org.jboss.tools.ui.bot.ext/src/org/jboss/tools/ui/bot/ext/types/PerspectiveType.java trunk/jst/tests/org.jboss.tools.ui.bot.ext/src/org/jboss/tools/ui/bot/ext/types/ViewType.java Log: Added tests of opening Drools perspective and synchronization between Rule Flow editor and Properties View. Modified: trunk/drools/tests/org.jboss.tools.drools.ui.bot.test/src/org/jboss/tools/drools/ui/bot/test/DroolsAllBotTests.java =================================================================== --- trunk/drools/tests/org.jboss.tools.drools.ui.bot.test/src/org/jboss/tools/drools/ui/bot/test/DroolsAllBotTests.java 2010-05-11 17:13:07 UTC (rev 22015) +++ trunk/drools/tests/org.jboss.tools.drools.ui.bot.test/src/org/jboss/tools/drools/ui/bot/test/DroolsAllBotTests.java 2010-05-11 18:37:27 UTC (rev 22016) @@ -22,6 +22,7 @@ import org.jboss.tools.drools.ui.bot.test.smoke.ManageDroolsProject; import org.jboss.tools.drools.ui.bot.test.smoke.ManageDroolsRules; import org.jboss.tools.drools.ui.bot.test.smoke.DroolsRulesEditorTest; +import org.jboss.tools.drools.ui.bot.test.smoke.OpenDroolsPerspective; import org.jboss.tools.drools.ui.bot.test.smoke.RuleFlowTest; import org.jboss.tools.ui.bot.ext.SWTTestExt; import org.jboss.tools.ui.bot.ext.SWTUtilExt; @@ -41,7 +42,8 @@ * */ @RunWith(Suite.class) -(a)SuiteClasses({ManageDroolsRuntime.class, +(a)SuiteClasses({OpenDroolsPerspective.class, + ManageDroolsRuntime.class, ManageDroolsProject.class, ManageDroolsRules.class, DroolsRulesEditorTest.class, Added: trunk/drools/tests/org.jboss.tools.drools.ui.bot.test/src/org/jboss/tools/drools/ui/bot/test/smoke/OpenDroolsPerspective.java =================================================================== --- trunk/drools/tests/org.jboss.tools.drools.ui.bot.test/src/org/jboss/tools/drools/ui/bot/test/smoke/OpenDroolsPerspective.java (rev 0) +++ trunk/drools/tests/org.jboss.tools.drools.ui.bot.test/src/org/jboss/tools/drools/ui/bot/test/smoke/OpenDroolsPerspective.java 2010-05-11 18:37:27 UTC (rev 22016) @@ -0,0 +1,50 @@ + /******************************************************************************* + * Copyright (c) 2007-2010 Red Hat, Inc. + * Distributed under license by Red Hat, Inc. All rights reserved. + * This program is made available under the terms of the + * Eclipse Public License v1.0 which accompanies this distribution, + * and is available at http://www.eclipse.org/legal/epl-v10.html + * + * Contributor: + * Red Hat, Inc. - initial API and implementation + ******************************************************************************/ + +package org.jboss.tools.drools.ui.bot.test.smoke; + +import org.eclipse.swtbot.swt.finder.exceptions.WidgetNotFoundException; +import org.jboss.tools.ui.bot.ext.SWTTestExt; +import org.jboss.tools.ui.bot.ext.types.IDELabel; +import org.jboss.tools.ui.bot.ext.types.PerspectiveType; +import org.junit.Test; +/** + * Test opening perspective + * @author Vladimir Pakan + * + */ +public class OpenDroolsPerspective extends SWTTestExt{ + /** + * Test Opening Drools Rules + */ + @Test + public void testManageDroolsProject() { + openDroolsPerspective(); + } + /** + * Open Drools Perspective + */ + private void openDroolsPerspective(){ + eclipse.openPerspective(PerspectiveType.DROOLS); + boolean wasFound = false; + try{ + bot.toolbarDropDownButtonWithTooltip(IDELabel.Button.DROOLS_WORKBENCH); + wasFound = true; + } catch (WidgetNotFoundException wnfe){ + wasFound = false; + } + eclipse.openPerspective(PerspectiveType.JAVA); + assertTrue("Drools Perspective was not opened properly. Button " + + IDELabel.Button.DROOLS_WORKBENCH + " is not present in Workbench", + wasFound); + } +} + Property changes on: trunk/drools/tests/org.jboss.tools.drools.ui.bot.test/src/org/jboss/tools/drools/ui/bot/test/smoke/OpenDroolsPerspective.java ___________________________________________________________________ Name: svn:mime-type + text/plain Modified: trunk/drools/tests/org.jboss.tools.drools.ui.bot.test/src/org/jboss/tools/drools/ui/bot/test/smoke/RuleFlowTest.java =================================================================== --- trunk/drools/tests/org.jboss.tools.drools.ui.bot.test/src/org/jboss/tools/drools/ui/bot/test/smoke/RuleFlowTest.java 2010-05-11 17:13:07 UTC (rev 22015) +++ trunk/drools/tests/org.jboss.tools.drools.ui.bot.test/src/org/jboss/tools/drools/ui/bot/test/smoke/RuleFlowTest.java 2010-05-11 18:37:27 UTC (rev 22016) @@ -28,6 +28,8 @@ import org.eclipse.swtbot.eclipse.gef.finder.widgets.SWTBotGefEditor; import org.eclipse.swtbot.swt.finder.finders.UIThreadRunnable; import org.eclipse.swtbot.swt.finder.results.Result; +import org.eclipse.swtbot.swt.finder.widgets.SWTBotTable; +import org.eclipse.swtbot.swt.finder.widgets.SWTBotTree; import org.eclipse.swtbot.swt.finder.widgets.SWTBotTreeItem; import org.jboss.tools.drools.ui.bot.test.DroolsAllBotTests; import org.jboss.tools.ui.bot.ext.SWTEclipseExt; @@ -35,6 +37,7 @@ import org.jboss.tools.ui.bot.ext.SWTUtilExt; import org.jboss.tools.ui.bot.ext.helper.KeyboardHelper; import org.jboss.tools.ui.bot.ext.types.IDELabel; +import org.jboss.tools.ui.bot.ext.types.ViewType; import org.junit.Test; import org.w3c.dom.Document; import org.w3c.dom.Element; @@ -139,6 +142,15 @@ gefEditor.mouseMoveLeftClick(xspacing + xoffset + 5, yoffset + 5); gefEditor.save(); checkFullRFFile(DroolsAllBotTests.DROOLS_PROJECT_NAME , ruleFlowFileName); + // check synchronization with Properties View + gefEditor.activateTool("Select"); + gefEditor.mouseMoveLeftClick(xoffset + 5, yoffset + 5); + SWTBotTree tree = eclipse.showView(ViewType.PROPERTIES).tree(); + String id = tree.getTreeItem("Id").cell(1); + String name = tree.getTreeItem("Name").cell(1); + assertTrue("First editor element has to have Id=1 and Name=Start." + + "\nBut it has Id=" + id + + " Name=" + name, id.equals("1") && name.equals("Start")); // Delete each component gefEditor.activateTool("Select"); for (int toolIndex = 0;toolIndex < tools.length;toolIndex++){ Modified: trunk/jst/tests/org.jboss.tools.ui.bot.ext/src/org/jboss/tools/ui/bot/ext/SWTEclipseExt.java =================================================================== --- trunk/jst/tests/org.jboss.tools.ui.bot.ext/src/org/jboss/tools/ui/bot/ext/SWTEclipseExt.java 2010-05-11 17:13:07 UTC (rev 22015) +++ trunk/jst/tests/org.jboss.tools.ui.bot.ext/src/org/jboss/tools/ui/bot/ext/SWTEclipseExt.java 2010-05-11 18:37:27 UTC (rev 22016) @@ -162,6 +162,9 @@ case GUVNOR_REPOSITORY_EXPLORING: perspectiveLabel = IDELabel.SelectPerspectiveDialog.GUVNOR_REPOSITORY_EXPLORING; break; + case DROOLS: + perspectiveLabel = IDELabel.SelectPerspectiveDialog.DROOLS; + break; default: fail("Unknown perspective to open"); } Modified: trunk/jst/tests/org.jboss.tools.ui.bot.ext/src/org/jboss/tools/ui/bot/ext/types/IDELabel.java =================================================================== --- trunk/jst/tests/org.jboss.tools.ui.bot.ext/src/org/jboss/tools/ui/bot/ext/types/IDELabel.java 2010-05-11 17:13:07 UTC (rev 22015) +++ trunk/jst/tests/org.jboss.tools.ui.bot.ext/src/org/jboss/tools/ui/bot/ext/types/IDELabel.java 2010-05-11 18:37:27 UTC (rev 22016) @@ -93,6 +93,7 @@ public static final String REMOVE = "Remove"; public static final String EDIT = "Edit..."; public static final String ADD_WITHOUT_DOTS = "Add"; + public static final String DROOLS_WORKBENCH = "Drools workbench"; } public class Shell { @@ -187,6 +188,7 @@ public static final String PROBLEMS = "Problems"; public static final String DEBUG = "Debug"; public static final String GUVNOR_REPOSITORIES = "Guvnor Repositories"; + public static final String PROPERTIES = "Properties"; } public class ViewGroup { @@ -208,6 +210,7 @@ public static final String JPA = "JPA"; public static final String DEBUG = "Debug"; public static final String GUVNOR_REPOSITORY_EXPLORING = "Guvnor Repository Exploring"; + public static final String DROOLS = "Drools"; } /** * Hibernate Console Wizard (ConsoleConfigurationCreationWizard) Labels ( Modified: trunk/jst/tests/org.jboss.tools.ui.bot.ext/src/org/jboss/tools/ui/bot/ext/types/PerspectiveType.java =================================================================== --- trunk/jst/tests/org.jboss.tools.ui.bot.ext/src/org/jboss/tools/ui/bot/ext/types/PerspectiveType.java 2010-05-11 17:13:07 UTC (rev 22015) +++ trunk/jst/tests/org.jboss.tools.ui.bot.ext/src/org/jboss/tools/ui/bot/ext/types/PerspectiveType.java 2010-05-11 18:37:27 UTC (rev 22016) @@ -16,6 +16,7 @@ * */ public enum PerspectiveType { - SEAM, JAVA, WEB_DEVELOPMENT, HIBERNATE, DB_DEVELOPMENT, JPA, DEBUG, GUVNOR_REPOSITORY_EXPLORING; + SEAM, JAVA, WEB_DEVELOPMENT, HIBERNATE, DB_DEVELOPMENT, JPA, DEBUG, GUVNOR_REPOSITORY_EXPLORING, + DROOLS; } Modified: trunk/jst/tests/org.jboss.tools.ui.bot.ext/src/org/jboss/tools/ui/bot/ext/types/ViewType.java =================================================================== --- trunk/jst/tests/org.jboss.tools.ui.bot.ext/src/org/jboss/tools/ui/bot/ext/types/ViewType.java 2010-05-11 17:13:07 UTC (rev 22015) +++ trunk/jst/tests/org.jboss.tools.ui.bot.ext/src/org/jboss/tools/ui/bot/ext/types/ViewType.java 2010-05-11 18:37:27 UTC (rev 22016) @@ -19,7 +19,7 @@ */ public enum ViewType { PACKAGE_EXPLORER, PROJECT_EXPLORER, WELCOME, DATA_SOURCE_EXPLORER, - SERVERS,WEB_PROJECTS,PROBLEMS,DEBUG,GUVNOR_REPOSITORIES; + SERVERS,WEB_PROJECTS,PROBLEMS,DEBUG,GUVNOR_REPOSITORIES,PROPERTIES; public String getGroupLabel() { @@ -33,6 +33,7 @@ case PROBLEMS: viewLabel = IDELabel.ViewGroup.GENERAL; break; case DEBUG: viewLabel = IDELabel.ViewGroup.DEBUG; break; case GUVNOR_REPOSITORIES: viewLabel = IDELabel.ViewGroup.GUVNOR; break; + case PROPERTIES: viewLabel = IDELabel.ViewGroup.GENERAL; break; default: fail("Unknown View Type"); } return viewLabel; @@ -49,6 +50,7 @@ case PROBLEMS: viewLabel = IDELabel.View.PROBLEMS; break; case DEBUG: viewLabel = IDELabel.View.DEBUG; break; case GUVNOR_REPOSITORIES: viewLabel = IDELabel.View.GUVNOR_REPOSITORIES; break; + case PROPERTIES: viewLabel = IDELabel.View.PROPERTIES; break; default: fail("Unknown View Type"); } return viewLabel;

15 years, 11 months

1
0
0 / 0

JBoss Tools SVN: r22015 - trunk/seam/tests/org.jboss.tools.seam.core.test/src/org/jboss/tools/seam/core/test.

by jbosstools-commits＠lists.jboss.org

Author: dazarov Date: 2010-05-11 13:13:07 -0400 (Tue, 11 May 2010) New Revision: 22015 Modified: trunk/seam/tests/org.jboss.tools.seam.core.test/src/org/jboss/tools/seam/core/test/SeamValidatorsTest.java Log: https://jira.jboss.org/jira/browse/JBIDE-6264 Modified: trunk/seam/tests/org.jboss.tools.seam.core.test/src/org/jboss/tools/seam/core/test/SeamValidatorsTest.java =================================================================== --- trunk/seam/tests/org.jboss.tools.seam.core.test/src/org/jboss/tools/seam/core/test/SeamValidatorsTest.java 2010-05-11 16:11:41 UTC (rev 22014) +++ trunk/seam/tests/org.jboss.tools.seam.core.test/src/org/jboss/tools/seam/core/test/SeamValidatorsTest.java 2010-05-11 17:13:07 UTC (rev 22015) @@ -746,7 +746,7 @@ } // See https://jira.jboss.org/jira/browse/JBIDE-4515 - public void testRevalidationUnresolvedELs() { + public void testRevalidationUnresolvedELs() throws CoreException{ refreshProject(project); JSFModelPlugin.getDefault().getPreferenceStore().setValue(JSFSeverityPreferences.RE_VALIDATE_UNRESOLVED_EL, SeamPreferences.ENABLE); JSFModelPlugin.getDefault().getPreferenceStore().setValue(JSFSeverityPreferences.UNKNOWN_EL_VARIABLE_NAME, SeamPreferences.ERROR); @@ -758,8 +758,9 @@ refreshProject(project); - int n = getMarkersNumber(xhtmlFile, SEAM_MARKER_FILTER); - assertEquals("There should be an unresolved EL in testElRevalidation.xhtml.", 1, n); + IMarker[] markers = findMarkers(xhtmlFile, IMarker.PROBLEM, "\"testElRevalidation\" cannot be resolved"); + assertEquals("There should be an unresolved EL in testElRevalidation.xhtml.", 1, markers.length); + JSFModelPlugin.getDefault().getPreferenceStore().setValue(JSFSeverityPreferences.RE_VALIDATE_UNRESOLVED_EL, SeamPreferences.DISABLE); // Check if the validator was not invoked. @@ -767,8 +768,8 @@ refreshProject(project); - n = getMarkersNumber(xhtmlFile, SEAM_MARKER_FILTER); - assertEquals("There should be an unresolved EL in testElRevalidation.xhtml.", 1, n); + markers = findMarkers(xhtmlFile, IMarker.PROBLEM, "\"testElRevalidation\" cannot be resolved"); + assertEquals("There should be an unresolved EL in testElRevalidation.xhtml.", 1, markers.length); JSFModelPlugin.getDefault().getPreferenceStore().setValue(JSFSeverityPreferences.RE_VALIDATE_UNRESOLVED_EL, SeamPreferences.ENABLE); JSFModelPlugin.getDefault().getPreferenceStore().setValue(JSFSeverityPreferences.UNKNOWN_EL_VARIABLE_NAME, SeamPreferences.IGNORE);

15 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbosstools-commits May 2010