Author: irooskov(a)redhat.com Date: 2011-10-04 20:23:37 -0400 (Tue, 04 Oct 2011) New Revision: 35348 Modified: branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/4.1.1_Release_Notes.xml branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Article_Info.xml branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Need_Info_Issues.xml Log: updated with new issues Modified: branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/4.1.1_Release_Notes.xml =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/4.1.1_Release_Notes.xml 2011-10-05 00:23:20 UTC (rev 35347) +++ branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/4.1.1_Release_Notes.xml 2011-10-05 00:23:37 UTC (rev 35348) @@ -2,7 +2,7 @@ <article> <xi:include href="Article_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> - <xi:include href="Need_Info_Issues.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> + <!-- <xi:include href="Need_Info_Issues.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> --> <xi:include href="Overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> <xi:include href="Component_Versions.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> <xi:include href="Fixed_Issues.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> Modified: branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Article_Info.xml =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Article_Info.xml 2011-10-05 00:23:20 UTC (rev 35347) +++ branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Article_Info.xml 2011-10-05 00:23:37 UTC (rev 35348) @@ -8,7 +8,7 @@ <productname>JBoss Developer Studio</productname> <productnumber>4.1</productnumber> <edition>4.1.1</edition> - <pubsnumber>24</pubsnumber> + <pubsnumber>26</pubsnumber> <abstract> <para> These release notes contain important information related to the JBoss Developer Studio. New features, known issues, resources, and other current issues are addressed here. Modified: branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml 2011-10-05 00:23:20 UTC (rev 35347) +++ branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml 2011-10-05 00:23:37 UTC (rev 35348) @@ -440,11 +440,16 @@ <itemizedlist> <listitem> <para> - <ulink url="http://jira.jboss.com/jira/browse/JBIDE-1781">JBIDE-178...;: When using the toolset on Ubuntu 11.04 with the Unity interface, only the <guilabel>Window</guilabel> menu item would appear in the top menu bar of the JBoss Developer Studio workspace. For the user this meant that all other menu functions were absent (for example, all options in the <guilabel>File</guilabel> and <guilabel> Edit</guilabel> menus). To correct the issue a new script is distributed with this JBoss Developer Studio release called <filename>jbdevstudio-unity</filename> that sets the environment variable <property>UBUNTU_MENUPROXY=0</property> prior to launching JBoss Developer Studio. By result of this script running is that Ubuntu Unity is forced to disable the global menu for JBoss Developer Studio, enabling the normal JBoss Developer Studio menu to be shown (containing all the usual menu options such as <guilabel>File</guilabel> and <guilabel> Edit</guilabel>). All other appli! cation windows within Ubuntu Unity remain unaffected. + <ulink url="http://jira.jboss.com/jira/browse/JBDS-1844">JBDS-1844&...;: The automated installer for JBoss Developer Studio did not record the preferred Java Runtime Environment (JRE) for reuse when the preferred JRE is not available on the <property>PATH</property> environment variable. This caused automated installations on Windows to fail. The issue has been rectified by modifying the installer to record the selected JRE path into the <filename>InstallConfigRecord.xml</filename> file, which is used during automated installation. Automated installation of JBoss Developer Studio no longer fails on the Windows operating system. </para> </listitem> <listitem> <para> + <ulink url="http://jira.jboss.com/jira/browse/JBDS-1781">JBDS-1781&...;: When using the toolset on Ubuntu 11.04 with the Unity interface, only the <guilabel>Window</guilabel> menu item would appear in the top menu bar of the JBoss Developer Studio workspace. For the user this meant that all other menu functions were absent (for example, all options in the <guilabel>File</guilabel> and <guilabel> Edit</guilabel> menus). To correct the issue a new script is distributed with this JBoss Developer Studio release called <filename>jbdevstudio-unity</filename> that sets the environment variable <property>UBUNTU_MENUPROXY=0</property> prior to launching JBoss Developer Studio. By result of this script running is that Ubuntu Unity is forced to disable the global menu for JBoss Developer Studio, enabling the normal JBoss Developer Studio menu to be shown (containing all the usual menu options such as <guilabel>File</guilabel> and <guilabel> Edit</guilabel>). All other applica! tion windows within Ubuntu Unity remain unaffected. + </para> + </listitem> + <listitem> + <para> <ulink url="http://jira.jboss.com/jira/browse/JBIDE-9514">JBIDE-951...;: Project Example ZIP files that contain empty folders, would not be imported correctly and the empty folders would be excluded, though they are necessary for the project to work (for example, the <filename>src</filename> folder). To fix this issue the <filename>NewProjectExamplesWizard.java</filename> has been modified to allow for empty folders within ZIP files to be imported correctly. </para> </listitem> Modified: branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Need_Info_Issues.xml =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Need_Info_Issues.xml 2011-10-05 00:23:20 UTC (rev 35347) +++ branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Need_Info_Issues.xml 2011-10-05 00:23:37 UTC (rev 35348) @@ -308,22 +308,22 @@ </itemizedlist> </para> </formalpara>--> - <formalpara> +<!-- <formalpara> <title>General Issues</title> <para> <itemizedlist> <listitem> <para> - <ulink url="http://jira.jboss.com/jira/browse/JBDS-1844">JBDS-1844&...;: <emphasis>Developer</emphasis>: Denis Golovin. + <ulink url="http://jira.jboss.com/jira/browse/JBIDE-0000">JBIDE-000...;: <emphasis>Developer</emphasis>: </para> <para> - <emphasis>Title</emphasis>: Automated Installer Script Does Not Recored Preferred JRE + <emphasis>Title</emphasis>: </para> <para> - <emphasis>Question</emphasis>: Only a "fixed in trunk and 4.x branch" comment is given. No SVN/Fisheye links are recorded and no further information is provided. What was the cause of the issue? How was the issue fixed in the code? What is the result that the user will now see - does JBDS now start with the user-selected JRE? + <emphasis>Question</emphasis>: </para> </listitem> </itemizedlist> </para> - </formalpara> + </formalpara> --> </section>