[jbosstools-commits] JBoss Tools SVN: r42420 - trunk/documentation/guides/JBDS_Release_Notes/en-US.

[jbosstools-commits at lists.jboss.org]

Author: irooskov at redhat.com
Date: 2012-07-05 18:28:12 -0400 (Thu, 05 Jul 2012)
New Revision: 42420

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 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-05 21:59:55 UTC (rev 42419)
+++ trunk/documentation/guides/JBDS_Release_Notes/en-US/Article_Info.xml	2012-07-05 22:28:12 UTC (rev 42420)
@@ -8,7 +8,7 @@
 	<productname>JBoss Developer Studio</productname>
 	<productnumber>5.0</productnumber>
 	<edition>5.0.1</edition>
-	<pubsnumber>1</pubsnumber>
+	<pubsnumber>2</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-05 21:59:55 UTC (rev 42419)
+++ trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml	2012-07-05 22:28:12 UTC (rev 42420)
@@ -3,28 +3,39 @@
     <title>
         Enhancements and fixed issues in version 5.0.1
     </title>
-<variablelist>
-
-	<!-- JBIDE-12177 -->
+	<variablelist>
+		<!-- JBIDE-12177 -->
+		<varlistentry>
+		<term>
+			<ulink url="https://issues.jboss.org/jira/browse/JBIDE-12177">JBIDE-12177</ulink>
+		</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-12177">JBIDE-12177</ulink>
+		<ulink url="https://issues.jboss.org/jira/browse/JBIDE-12158">JBIDE-12158</ulink>
 	</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.
+			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-12071 -->
    <varlistentry>
    <term>
-	   <ulink url="https://issues.jboss.org/jira/browse/JBIDE-12158">JBIDE-12158</ulink>
+	   <ulink url="https://issues.jboss.org/jira/browse/JBIDE-12071">JBIDE-12071</ulink>
    </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.
+         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>