JBoss Tools SVN: r20390 - in trunk/documentation/guides/MigrationGuide/en: modules and 1 other directory.
10:06 a.m.
Author: ochikvina
Date: 2010-02-19 11:06:36 -0500 (Fri, 19 Feb 2010)
New Revision: 20390
Added:
trunk/documentation/guides/MigrationGuide/en/images/jdbs2.png
trunk/documentation/guides/MigrationGuide/en/images/jdbs4.png
trunk/documentation/guides/MigrationGuide/en/images/migration-guide-step-1.png
trunk/documentation/guides/MigrationGuide/en/modules/introduction.xml
trunk/documentation/guides/MigrationGuide/en/modules/issues.xml
trunk/documentation/guides/MigrationGuide/en/modules/migration.xml
Log:
<html><head><meta name="qrichtext" content="1"
/></head><body style="font-size:9pt;font-family:Sans Serif">
<p>https://jira.jboss.org/jira/browse/JBDS-1062 - Added the first version of the
guide.</p>
</body></html>
Added: trunk/documentation/guides/MigrationGuide/en/images/jdbs2.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/guides/MigrationGuide/en/images/jdbs2.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/documentation/guides/MigrationGuide/en/images/jdbs4.png
===================================================================
(Binary files differ)
Property changes on: trunk/documentation/guides/MigrationGuide/en/images/jdbs4.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/documentation/guides/MigrationGuide/en/images/migration-guide-step-1.png
===================================================================
(Binary files differ)
Property changes on:
trunk/documentation/guides/MigrationGuide/en/images/migration-guide-step-1.png
___________________________________________________________________
Name: svn:mime-type
+ application/octet-stream
Added: trunk/documentation/guides/MigrationGuide/en/modules/introduction.xml
===================================================================
--- trunk/documentation/guides/MigrationGuide/en/modules/introduction.xml
(rev 0)
+++ trunk/documentation/guides/MigrationGuide/en/modules/introduction.xml 2010-02-19
16:06:36 UTC (rev 20390)
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="introduction" xreflabel="introduction">
+ <?dbhtml filename="introduction.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>JBDS</keyword>
+ <keyword>Exadel Studio Pro</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Introduction </title>
+ <para>This document is intended to help you to easily migrate from 2.1 to 3.0.0
+ <property>JBoss Developer Studio</property>.
+ It also describes some popular issues that can appear while the process of migration,
+ as well as the methods of their solving. </para>
+
+
+ <section>
+ <title>Other relevant resources on the topic</title>
+ <para>All JBoss Developer Studio release documentation you can find at <ulink
url="http://www.redhat.com/docs/en-US/JBoss_Developer_Studio/"&...
in the corresponding release directory.</para>
+ <para>For more information about JBoss Developer Studio please visit
+ <ulink
url="http://www.jboss.com/products/devstudio/">http://www.jb...
+ <para>If your problem is not described in the guide or you have questions or
suggestions concerned both the documentation and studio behavior, you are welcome at
<ulink
url="http://community.jboss.org/en/jbossdevstudio?view=discussions&q...
Users forum</ulink>.
+ </para>
+ </section>
+</chapter>
Property changes on:
trunk/documentation/guides/MigrationGuide/en/modules/introduction.xml
___________________________________________________________________
Name: svn:executable
+ *
Added: trunk/documentation/guides/MigrationGuide/en/modules/issues.xml
===================================================================
--- trunk/documentation/guides/MigrationGuide/en/modules/issues.xml
(rev 0)
+++ trunk/documentation/guides/MigrationGuide/en/modules/issues.xml 2010-02-19 16:06:36
UTC (rev 20390)
@@ -0,0 +1,41 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="issues" xreflabel="issues">
+ <?dbhtml filename="introduction.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>JBDS</keyword>
+ <keyword>Exadel Studio Pro</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Possible issues</title>
+ <para>In this chapter you will find a list of most popular
+ issues that can appear while the process of migration,
+ </para>
+
+
+ <section>
+ <title>Visual Editor starts with "Missing Natures" message
dialog</title>
+ <para>While opening existing projects or creating new ones
+ with some standard eclipse wizards this message can appear:</para>
+ <figure>
+ <title>"Missing Natures" message</title>
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jdbs4.png" />
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>This message shows that some functionality of Visual Editor may not
work if a project
+ doesn't have org.jboss.tools.jsf.jsfnature or
org.jboss.tools.jst.web.kb.kbnature
+ in .project configuration. To fix this problem and turn off the message box
execute the following steps:</para>
+ <itemizedlist>
+ <listitem><para>Right click the project in Package
Explorer.</para></listitem>
+ <listitem><para>Select <property>Configure -> Add JSF
Capabilities</property> from the context menu.</para></listitem>
+ <listitem><para>Configure your project using Add JSF Capabilities
wizard and press <property>Finish</property></para></listitem>
+ </itemizedlist>
+ </section>
+
+
+</chapter>
Added: trunk/documentation/guides/MigrationGuide/en/modules/migration.xml
===================================================================
--- trunk/documentation/guides/MigrationGuide/en/modules/migration.xml
(rev 0)
+++ trunk/documentation/guides/MigrationGuide/en/modules/migration.xml 2010-02-19 16:06:36
UTC (rev 20390)
@@ -0,0 +1,56 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<chapter id="jsf_struts" xreflabel="jsf_struts">
+ <?dbhtml filename="jsf_struts.html"?>
+ <chapterinfo>
+ <keywordset>
+ <keyword>JBoss Developer Studio</keyword>
+ <keyword>JBDS</keyword>
+ <keyword>Exadel Studio Pro</keyword>
+ <keyword>Migration</keyword>
+ </keywordset>
+ </chapterinfo>
+
+ <title>Migration Process</title>
+ <para>In this chapter you can find concise description of JBoss Developer
Studio migration from
+ 2.1.0 to 3.0.0 version.</para>
+ <section id="migration">
+ <title>How to migrate from 2.1 to 3.0.0 JBoss Developer
Studio</title>
+ <para></para>
+ <para>To migrate from 2.1 to 3.0.0 you have to install a fresh JBDS 3.0.0
and go through all the steps of
+ installation process that is fully described in
+ <ulink url="gsglink">Getting Started with JBoss Developer
Studio</ulink> guide.</para>
+ <figure>
+ <title>Process of JBDS 3.0.0 installation </title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/jdbs2.png" />
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>Now you can not update your JBDS 2.X to 3.0.0 using update
site(https://devstudio.jboss.com/updates/3.0/ ), as it was available in previous
versions:</para>
+ <figure>
+ <title>Installation from the update site</title>
+
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/migration-guide-step-1.png"
/>
+ </imageobject>
+ </mediaobject>
+ </figure>
+ <para>The reason is that JBDS 3.0 uses Eclipse 3.5, whereas JBDS 2.x uses
Eclipse 3.4.
+ Because of this platform change, a full install is required to migrate.
</para>
+ <para>When the installation process is complete you can point your JBDS
3.0.0 at your old workspace directory and continue working with your projects created
using previous
+ JBDS/Tools versions, or create a new one and import old projects into the new
workspace.
+ </para>
+
+ <note>
+ <title>Note:</title>
+ <para>In JBDS 3.0.0 Lunux users no longer need to install the library
libstdc+.so.5 on their mashines.
+ Now this library is not required and can be removed from the system.
+ </para>
+ </note>
+ </section>
+
+
+</chapter>
5909
days inactive
5909
days old
jbosstools-commits@lists.jboss.org
0 comments
1 participants
participants (1)
-
jbosstools-commits＠lists.jboss.org