Author: irooskov(a)redhat.com Date: 2012-07-10 21:57:13 -0400 (Tue, 10 Jul 2012) New Revision: 42499 Modified: trunk/documentation/guides/JBDS_Release_Notes/en-US/Article_Info.xml trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml Log: updated with new fixed issues for JBDs 5.0.1 Modified: trunk/documentation/guides/JBDS_Release_Notes/en-US/Article_Info.xml =================================================================== --- trunk/documentation/guides/JBDS_Release_Notes/en-US/Article_Info.xml 2012-07-10 22:23:52 UTC (rev 42498) +++ trunk/documentation/guides/JBDS_Release_Notes/en-US/Article_Info.xml 2012-07-11 01:57:13 UTC (rev 42499) @@ -8,7 +8,7 @@ <productname>JBoss Developer Studio</productname> <productnumber>5.0</productnumber> <edition>5.0.1</edition> - <pubsnumber>3</pubsnumber> + <pubsnumber>4</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: trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml =================================================================== --- trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml 2012-07-10 22:23:52 UTC (rev 42498) +++ trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml 2012-07-11 01:57:13 UTC (rev 42499) @@ -3,43 +3,73 @@ <title> Enhancements and fixed issues in version 5.0.1 </title> -<variablelist> - <!-- JBIDE-12177 --> - <varlistentry> - <term><ulink url="https://issues.jboss.org/jira/browse/JBIDE-12177">JBIDE... - <listitem> - <para> - The feature to auto-complete code tags was broken in the Visual Editor. When attempting to auto-complete a code tag, invalid code would be generated. This has been corrected by modifying the content assist file XmlTagCompletionProposalComputer.java to ensure partner code tags are generated correctly when using auto-completion. - </para> - </listitem> - </varlistentry> + <variablelist> + <!-- JBIDE-12177 --> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/jira/browse/JBIDE-12177">JBIDE... + </term> + <listitem> + <para> + The feature to auto-complete code tags was broken in the Visual Editor. When attempting to auto-complete a code tag, invalid code would be generated. This has been corrected by modifying the content assist file XmlTagCompletionProposalComputer.java to ensure partner code tags are generated correctly when using auto-completion. + </para> + </listitem> + </varlistentry> + + <!-- JBIDE-12158 --> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/jira/browse/JBIDE-12158">JBIDE... + </term> + <listitem> + <para> + An issue existed when creating a Dynamic Web Project and modifying the project to include the JBoss Core Portlet facet to the project. The portlet-api library was not detected in the target runtime, forcing the user to manually specify it via the user library. This has been corrected by adding the option, Portlet Target Runtime Provider, to the combo-box on the JBoss Portlet Capabilities wizard page. + </para> + </listitem> +</varlistentry> - <!-- JBIDE-12158 --> + <!-- JBIDE-12111 --> <varlistentry> - <term><ulink url="https://issues.jboss.org/jira/browse/JBIDE-12158">JBIDE... - <listitem> - <para> - An issue existed when creating a Dynamic Web Project and modifying the project to include the JBoss Core Portlet facet to the project. The portlet-api library was not detected in the target runtime, forcing the user to manually specify it via the user library. This has been corrected by adding the option, Portlet Target Runtime Provider, to the combo-box on the JBoss Portlet Capabilities wizard page. - </para> - </listitem> + <term> + <ulink url="https://issues.jboss.org/jira/browse/JBIDE-12111">JBIDE... + </term> + <listitem> + <para> + The version of Java to be used was hard coded in the pom.xml file of Maven projects. This caused errors when adding Maven configuration to a Seam 2.3 project since Maven projects were created to use Java 1.5, however Seam 2.3 requires Java 1.6. Maven tooling has been updated to allow the maven-compiler-plugin settings that are in the parent project to be dynamically inferred from the converted web project's original settings. This ensures the correct Java version is retained when Maven integration is added to an existing project. + </para> + </listitem> </varlistentry> - + <!-- JBIDE-12071 --> <varlistentry> - <term><ulink url="https://issues.jboss.org/jira/browse/JBIDE-12071">JBIDE... - <listitem> - <para> - Previously, when a user performed a drag-and-drop action to publish a project it was ignored. This occurred because the code to publish a project only accepted direct user-initiated actions and not those considered to be a shell action. The ExpressPublishMethod.java and ExpressBehaviour.java files have been updated to handle shell actions correctly. As a result, incremental publishes initiated by the user are now also handled correctly. - </para> - </listitem> + <term> + <ulink url="https://issues.jboss.org/jira/browse/JBIDE-12071">JBIDE... + </term> + <listitem> + <para> + Previously, when a user performed a drag-and-drop action to publish a project it was ignored. This occurred because the code to publish a project only accepted direct user-initiated actions and not those considered to be a shell action. The ExpressPublishMethod.java and ExpressBehaviour.java files have been updated to handle shell actions correctly. As a result, incremental publishes initiated by the user are now also handled correctly. + </para> + </listitem> </varlistentry> - + <!-- JBIDE-12046 --> <varlistentry> - <term><ulink url="https://issues.jboss.org/jira/browse/JBIDE-12046">JBIDE... + <term> + <ulink url="https://issues.jboss.org/jira/browse/JBIDE-12046">JBIDE... + </term> + <listitem> + <para> + When a user tried to start or deploy to a remote server that was no longer reachable, various errors would be returned, however no adequate description of the issue was communicated. This issue has been resolved by returning a descriptive error when the remote server is unreachable and checking for file system responsiveness before attempting to publish. + </para> + </listitem> + </varlistentry> + + <!-- JBIDE-11310 --> + <varlistentry> + <term><ulink url="https://issues.jboss.org/jira/browse/JBIDE-11310">JBIDE... <listitem> <para> - When a user tried to start or deploy to a remote server that was no longer reachable, various errors would be returned, however no adequate description of the issue was communicated. This issue has been resolved by returning a descriptive error when the remote server is unreachable and checking for file system responsiveness before attempting to publish. + An issue in the OpenShift tooling meant that if a user logged into OpenShift and created an application, then went back to the login screen and signed in as a different user, the previous application parameters would still be available. This meant the second user was not able to create an application with the same parameters, and was also able to view what the previous user had created, causing a potential security issue. OpenShift tooling has been updated to reset when a new user connects, triggering a refresh of the targets and parameters. </para> </listitem> </varlistentry> @@ -47,4 +77,5 @@ </variablelist> + </section>