[jbosstools-commits] JBoss Tools SVN: r22536 - trunk/documentation/guides/JBDS_Release_Notes/en-US.
jbosstools-commits at lists.jboss.org
jbosstools-commits at lists.jboss.org
Thu Jun 3 20:50:18 EDT 2010
Author: irooskov at redhat.com
Date: 2010-06-03 20:50:17 -0400 (Thu, 03 Jun 2010)
New Revision: 22536
Modified:
trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml
trunk/documentation/guides/JBDS_Release_Notes/en-US/Known_Issues.xml
trunk/documentation/guides/JBDS_Release_Notes/en-US/Release_Notes.xml
Log:
updated to take 1222 from known issues to fixed
Modified: trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml
===================================================================
--- trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml 2010-06-04 00:44:40 UTC (rev 22535)
+++ trunk/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml 2010-06-04 00:50:17 UTC (rev 22536)
@@ -214,6 +214,11 @@
<ulink url="http://jira.jboss.com/jira/browse/JBDS-1168">JBDS-1168</ulink>: The JBoss Developer Studio Installer was missleading in terms of system requirements. The consequence of this was that some users were unsure if the JBoss Developer Studio supported Java 6 even though it was required for the JBoss Enterprise Application Platform 5 and which JDK distributions were supported. The text in Step 4 of installation has been updated to inform the user that the JBoss Developer Studio works with both Java 5 and 6 (though Java 6 is required for JBoss Enterprise Application Platform 5), has been tested with the OpenJDK, SunJDK and IBM JDK distributions and the misspelt <emphasis>gij Java</emphasis> has been corrected to <emphasis>gcj Java</emphasis>.
</para>
</listitem>
+ <listitem>
+ <para>
+ <ulink url="https://jira.jboss.org/jira/browse/JBDS-1222">JBDS-1222</ulink>: A bug existed in the JBoss Developer Studio that caused stylesheets to not render correctly in the JBoss Enterprise Application Platform 5 and a <exceptionname>org.ajax4jsf.resource.ResourceNotFoundException: Static resource not found for path <resource name></exceptionname> exception when using the JBoss Enterprise Portal Platform 5 to load a JSF page through a Portlet. These errors were caused by the code to load the style sheet being: <code><a:loadStyle src="resource:///stylesheet/theme.xcss"/></code> instead of <code><a:loadStyle src="/stylesheet/theme.xcss"/></code>. This issue has now been corrected for this release.
+ </para>
+ </listitem>
<!-- Reopened <listitem>
<para>
<ulink url="http://jira.jboss.com/jira/browse/JBDS-1147">JBDS-1147</ulink>: An incorrect link to the Guvnor Rules repository was included in the JBoss Developer Studio. This bug caused the repository to become unreachable. This has been fixed by correcting the link to be <ulink url="http://localhost:8080/drools-guvnor/org.drools.guvnor.Guvnor/webdav">http://localhost:8080/drools-guvnor/org.drools.guvnor.Guvnor/webdav</ulink>. The JBoss Developer Studio is now able to connect to the Guvnor Rules repository.
Modified: trunk/documentation/guides/JBDS_Release_Notes/en-US/Known_Issues.xml
===================================================================
--- trunk/documentation/guides/JBDS_Release_Notes/en-US/Known_Issues.xml 2010-06-04 00:44:40 UTC (rev 22535)
+++ trunk/documentation/guides/JBDS_Release_Notes/en-US/Known_Issues.xml 2010-06-04 00:50:17 UTC (rev 22536)
@@ -10,19 +10,7 @@
<title>General Known Issues</title>
<para>
<itemizedlist>
- <listitem>
- <para>
- <ulink url="https://jira.jboss.org/jira/browse/JBDS-1222">JBDS-1222</ulink>: A bug exists in the JBoss Developer Studio that causes stylesheets to not render correctly in the JBoss Enterprise Application Platform 5 and a <exceptionname>org.ajax4jsf.resource.ResourceNotFoundException: Static resource not found for path <resource name></exceptionname> exception when using the JBoss Enterprise Portal Platform 5 to load a JSF page through a Portlet. These errors are caused by the code to load the style sheet being: <code><a:loadStyle src="resource:///stylesheet/theme.xcss"/></code> instead of <code><a:loadStyle src="/stylesheet/theme.xcss"/></code>.
- </para>
- <para>
- The current workaround for this issue is to manually remove the code <code>resource://</code> from the beginning of the stylesheet location.
- </para>
- <note>
- <para>
- This issue does not present in the JBoss Enterprise Application Platform 4.3 because of a bug that exists in it that hides this issue.
- </para>
- </note>
- </listitem>
+
</itemizedlist>
</para>
</formalpara>
Modified: trunk/documentation/guides/JBDS_Release_Notes/en-US/Release_Notes.xml
===================================================================
--- trunk/documentation/guides/JBDS_Release_Notes/en-US/Release_Notes.xml 2010-06-04 00:44:40 UTC (rev 22535)
+++ trunk/documentation/guides/JBDS_Release_Notes/en-US/Release_Notes.xml 2010-06-04 00:50:17 UTC (rev 22536)
@@ -7,6 +7,6 @@
<xi:include href="Component_Versions.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
<xi:include href="Updating_to_the_new_Web_Tools_Platform_packages.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>
- <xi:include href="Known_Issues.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
+<!-- <xi:include href="Known_Issues.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> -->
<xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include>
</article>
More information about the jbosstools-commits
mailing list