JBoss Tools SVN: r35351 - in trunk/as/plugins: org.jboss.tools.openshift.express.client and 1 other directory.
by jbosstools-commits＠lists.jboss.org
Author: adietish
Date: 2011-10-05 06:54:19 -0400 (Wed, 05 Oct 2011)
New Revision: 35351
Added:
trunk/as/plugins/org.jboss.tools.openshift.express.client/
trunk/as/plugins/org.jboss.tools.openshift.express.client/org.jboss.tools.openshift.express.client.test/
trunk/as/plugins/org.jboss.tools.openshift.express.client/org.jboss.tools.openshift.express.client/
trunk/as/plugins/org.jboss.tools.openshift.express.client/org.jboss.tools.openshift.express.ui/
Log:
[JBIDE-9841] renamed org.jboss.ide.eclipse.as.openshift.core to org.jboss.tools.openshift.express.client
13 years, 3 months
JBoss Tools SVN: r35350 - trunk/documentation/guides/JBDS_Release_Notes/en-US.
by jbosstools-commits＠lists.jboss.org
Author: irooskov(a)redhat.com
Date: 2011-10-05 01:09:43 -0400 (Wed, 05 Oct 2011)
New Revision: 35350
Modified:
trunk/documentation/guides/JBDS_Release_Notes/en-US/Overview.xml
Log:
updated for JBDs 5
Modified: trunk/documentation/guides/JBDS_Release_Notes/en-US/Overview.xml
===================================================================
--- trunk/documentation/guides/JBDS_Release_Notes/en-US/Overview.xml 2011-10-05 04:59:17 UTC (rev 35349)
+++ trunk/documentation/guides/JBDS_Release_Notes/en-US/Overview.xml 2011-10-05 05:09:43 UTC (rev 35350)
@@ -20,6 +20,12 @@
<!-- https://issues.jboss.org/browse/JBIDE-9497 -->
</para>
</listitem>
+ <listitem>
+ <para>
+ Seam Servlet module support
+ <!-- https://issues.jboss.org/browse/JBIDE-9388 -->
+ </para>
+ </listitem>
</itemizedlist>
<important>
<para>
13 years, 3 months
JBoss Tools SVN: r35349 - trunk/esb/plugins/org.jboss.tools.esb.project.core/src/org/jboss/tools/esb/core/facet.
by jbosstools-commits＠lists.jboss.org
Author: rob.stryker(a)jboss.com
Date: 2011-10-05 00:59:17 -0400 (Wed, 05 Oct 2011)
New Revision: 35349
Modified:
trunk/esb/plugins/org.jboss.tools.esb.project.core/src/org/jboss/tools/esb/core/facet/JBossClassPathCommand.java
Log:
Uncommitted optimization from god knows how long ago.
Modified: trunk/esb/plugins/org.jboss.tools.esb.project.core/src/org/jboss/tools/esb/core/facet/JBossClassPathCommand.java
===================================================================
--- trunk/esb/plugins/org.jboss.tools.esb.project.core/src/org/jboss/tools/esb/core/facet/JBossClassPathCommand.java 2011-10-05 00:23:37 UTC (rev 35348)
+++ trunk/esb/plugins/org.jboss.tools.esb.project.core/src/org/jboss/tools/esb/core/facet/JBossClassPathCommand.java 2011-10-05 04:59:17 UTC (rev 35349)
@@ -18,19 +18,14 @@
import org.eclipse.core.runtime.IPath;
import org.eclipse.core.runtime.IProgressMonitor;
import org.eclipse.core.runtime.IStatus;
-import org.eclipse.core.runtime.NullProgressMonitor;
import org.eclipse.core.runtime.Path;
import org.eclipse.core.runtime.Status;
-import org.eclipse.jdt.core.IClasspathEntry;
-import org.eclipse.jdt.core.IJavaProject;
-import org.eclipse.jdt.core.JavaCore;
-import org.eclipse.jdt.core.JavaModelException;
-import org.eclipse.osgi.util.NLS;
import org.eclipse.wst.common.frameworks.datamodel.AbstractDataModelOperation;
import org.eclipse.wst.common.frameworks.datamodel.IDataModel;
import org.eclipse.wst.common.project.facet.core.IFacetedProject;
import org.eclipse.wst.common.project.facet.core.ProjectFacetsManager;
import org.eclipse.wst.common.project.facet.core.runtime.IRuntime;
+import org.jboss.ide.eclipse.as.wtp.core.vcf.VCFClasspathCommand;
import org.jboss.tools.esb.core.StatusUtils;
import org.jboss.tools.esb.core.messages.JBossFacetCoreMessages;
import org.jboss.tools.esb.core.runtime.JBossRuntimeClassPathInitializer;
@@ -112,44 +107,6 @@
* @return
*/
public static IStatus addClassPath(IProject project, IPath path) {
- IStatus status = Status.OK_STATUS;
- try {
-
- IClasspathEntry newClasspath;
- IJavaProject javaProject = JavaCore.create(project);
- newClasspath = JavaCore.newContainerEntry(path);
-
- IClasspathEntry[] oldClasspathEntries = javaProject
- .readRawClasspath();
-
- boolean isFolderInClassPathAlready = false;
- for (int i = 0; i < oldClasspathEntries.length
- && !isFolderInClassPathAlready; i++) {
- if (oldClasspathEntries[i].getPath().equals(
- newClasspath.getPath())) {
- isFolderInClassPathAlready = true;
- break;
- }
- }
-
- if (!isFolderInClassPathAlready) {
-
- IClasspathEntry[] newClasspathEntries = new IClasspathEntry[oldClasspathEntries.length + 1];
- for (int i = 0; i < oldClasspathEntries.length; i++) {
- newClasspathEntries[i] = oldClasspathEntries[i];
- }
- newClasspathEntries[oldClasspathEntries.length] = newClasspath;
- javaProject.setRawClasspath(newClasspathEntries,
- new NullProgressMonitor());
- }
- } catch (JavaModelException e) {
- status = StatusUtils.errorStatus(NLS.bind(
- JBossFacetCoreMessages.Error_Copy, new String[] { e
- .getLocalizedMessage() }), e);
- return status;
- }
-
- return status;
+ return VCFClasspathCommand.addClassPath(project, path);
}
-
}
\ No newline at end of file
13 years, 3 months
JBoss Tools SVN: r35348 - branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US.
by jbosstools-commits＠lists.jboss.org
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-1781</ulink>: 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</ulink>: 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</ulink>: 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-9514</ulink>: 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</ulink>: <emphasis>Developer</emphasis>: Denis Golovin.
+ <ulink url="http://jira.jboss.com/jira/browse/JBIDE-0000">JBIDE-0000</ulink>: <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>
13 years, 3 months
JBoss Tools SVN: r35347 - trunk/documentation/whatsnew/jst.
by jbosstools-commits＠lists.jboss.org
Author: akazakov
Date: 2011-10-04 20:23:20 -0400 (Tue, 04 Oct 2011)
New Revision: 35347
Modified:
trunk/documentation/whatsnew/jst/jst-news-3.3.0.M3.html
Log:
https://issues.jboss.org/browse/TOOLSDOC-260 Errors in What's New for JSF component v. 3.3.0.M3
Modified: trunk/documentation/whatsnew/jst/jst-news-3.3.0.M3.html
===================================================================
--- trunk/documentation/whatsnew/jst/jst-news-3.3.0.M3.html 2011-10-04 23:21:18 UTC (rev 35346)
+++ trunk/documentation/whatsnew/jst/jst-news-3.3.0.M3.html 2011-10-05 00:23:20 UTC (rev 35347)
@@ -46,7 +46,7 @@
(Ctrl+Click) and searching (Ctrl+Shift+G).</p>
<img src="images/3.3.0.M3/ca.png"/>
- <p>Wwith this existing
+ <p>With this existing
applications and examples will no longer have error
markers for EL expressions that refer to
@ManagedBeans. For new development consider use CDI
@@ -116,7 +116,7 @@
<p><b>Resources in related non-WTP projects</b></p>
</td>
<td valign=top>
- <p>If you project have resources in related
+ <p>If your project have resources in related
projects which does not have JBoss Tools Knowledgebase
Builder installed JBoss Tools cannot "see" the
resources inside these projects and you might get
13 years, 3 months
JBoss Tools SVN: r35346 - trunk/vpe/tests/org.jboss.tools.vpe.docbook.test/META-INF.
by jbosstools-commits＠lists.jboss.org
Author: dgolovin
Date: 2011-10-04 19:21:18 -0400 (Tue, 04 Oct 2011)
New Revision: 35346
Modified:
trunk/vpe/tests/org.jboss.tools.vpe.docbook.test/META-INF/MANIFEST.MF
Log:
removed dependency to vpe.ui.test to avoid skipping tests in case of vpe.ui.test failures
Modified: trunk/vpe/tests/org.jboss.tools.vpe.docbook.test/META-INF/MANIFEST.MF
===================================================================
--- trunk/vpe/tests/org.jboss.tools.vpe.docbook.test/META-INF/MANIFEST.MF 2011-10-04 23:17:07 UTC (rev 35345)
+++ trunk/vpe/tests/org.jboss.tools.vpe.docbook.test/META-INF/MANIFEST.MF 2011-10-04 23:21:18 UTC (rev 35346)
@@ -6,7 +6,6 @@
Bundle-Activator: org.jboss.tools.vpe.docbook.test.DocbookTestPlugin
Require-Bundle: org.eclipse.ui,
org.eclipse.core.runtime,
- org.jboss.tools.vpe.ui.test,
org.jboss.tools.common.text.ext,
org.jboss.tools.common.model,
org.jboss.tools.vpe.xulrunner,
13 years, 3 months
JBoss Tools SVN: r35345 - branches/jbosstools-3.2.x/build.
by jbosstools-commits＠lists.jboss.org
Author: dgolovin
Date: 2011-10-04 19:17:07 -0400 (Tue, 04 Oct 2011)
New Revision: 35345
Modified:
branches/jbosstools-3.2.x/build/pom.xml
Log:
fixed esb-bootstrap profile to include all required components
Modified: branches/jbosstools-3.2.x/build/pom.xml
===================================================================
--- branches/jbosstools-3.2.x/build/pom.xml 2011-10-04 22:54:31 UTC (rev 35344)
+++ branches/jbosstools-3.2.x/build/pom.xml 2011-10-04 23:17:07 UTC (rev 35345)
@@ -411,6 +411,11 @@
<id>esb-bootstrap</id>
<modules>
<module>../tests</module>
+ <module>../common</module>
+ <module>../jst</module>
+ <module>../jmx</module>
+ <module>../archives</module>
+ <module>../as</module>
<module>../esb</module>
</modules>
</profile>
13 years, 3 months
JBoss Tools SVN: r35342 - trunk/vpe/plugins/org.jboss.tools.vpe.xulrunner/src/org/jboss/tools/vpe/xulrunner/util.
by jbosstools-commits＠lists.jboss.org
Author: dgolovin
Date: 2011-10-04 18:44:50 -0400 (Tue, 04 Oct 2011)
New Revision: 35342
Modified:
trunk/vpe/plugins/org.jboss.tools.vpe.xulrunner/src/org/jboss/tools/vpe/xulrunner/util/XPCOM.java
Log:
Constant added with error code to distinguish NO_INTEFACE error from others
Modified: trunk/vpe/plugins/org.jboss.tools.vpe.xulrunner/src/org/jboss/tools/vpe/xulrunner/util/XPCOM.java
===================================================================
--- trunk/vpe/plugins/org.jboss.tools.vpe.xulrunner/src/org/jboss/tools/vpe/xulrunner/util/XPCOM.java 2011-10-04 22:25:30 UTC (rev 35341)
+++ trunk/vpe/plugins/org.jboss.tools.vpe.xulrunner/src/org/jboss/tools/vpe/xulrunner/util/XPCOM.java 2011-10-04 22:44:50 UTC (rev 35342)
@@ -56,6 +56,8 @@
public static final String NS_IWEBBROWSER_CID = "F1EAC761-87E9-11d3-AF80-00A024FFC08C"; //$NON-NLS-1$
public static final String NS_IAPPSHELL_CID = "2d96b3df-c051-11d1-a827-0040959a28c9"; //$NON-NLS-1$
+ public static final long NS_ERROR_NO_INTERFACE = 0x80004002L;
+
/**Stores all interfaces which extend nsISupports. */
/* Lazy initialization of interfacesList is used to avoid loading
* of all these classes (>1000) by the class loader. */
13 years, 3 months