Author: mcaspers Date: 2011-01-16 23:15:53 -0500 (Sun, 16 Jan 2011) New Revision: 28276 Modified: trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml Log: Added new JIRAs Modified: trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml =================================================================== --- trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml 2011-01-17 02:58:22 UTC (rev 28275) +++ trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml 2011-01-17 04:15:53 UTC (rev 28276) @@ -1265,6 +1265,12 @@ <itemizedlist> <listitem> + <para> + <ulink url="https://issues.jboss.org/browse/JBIDE-7527">JBIDE-7527&...;: The the new JBoss Tools Runtime Detection feature provides a way for JBoss runtime components such as jBPM, Drools, JBoss Server and Seam to be discovered when a workspace is created or when Eclipse is started. These runtime components can be found within a user definable list of directories, which can be defined in <menuchoice><guimenuitem>Preferences</guimenuitem><guimenuitem>JBoss Tools</guimenuitem><guimenuitem>JBoss Tools Runtime Detection</guimenuitem></menuchoice>. + </para> + </listitem> + + <listitem> <para> <ulink url="https://issues.jboss.org/browse/JBDS-1150">JBDS-1150<...;: The Java Virtual Machine used by the JBoss Developer Studio installer will also be used as the default VM for JBDS. This can casuse problems if a 64 bit Java VM is used to install a 32 bit JBDS distribution, as the two are incompatible. This can be fixed by editing the <filename>eclipse.ini</filename> file and modifying the <property>vm</property> argument, or by using the appropiate Java VM when installing JBDS. </para>