[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-releng-dev] [eclipse-build]Build I20060602-0010 (Timestamp: 200606020010):Automated JUnit testing complete. Test failures/errors occurred.
|
Patch for chkpii errors in pde.doc.user.
Could someone with the commit rights please release it? This would then
need to be versionned and tagged for the next rebuild.
Olivier
eclipse-releng@xxxxxxxxxxx
Sent by: platform-releng-dev-bounces@xxxxxxxxxxx
2006-06-02 12:31
Please respond to
"Eclipse platform release engineering list."
To
platform-releng-dev@xxxxxxxxxxx
cc
Subject
[platform-releng-dev] [eclipse-build]Build I20060602-0010 (Timestamp:
200606020010):Automated JUnit testing complete. Test failures/errors
occurred.
Build I20060602-0010 (Timestamp: 200606020010): Automated JUnit testing
is complete. Test failures/errors occurred in the following:
org.eclipse.jdt.debug.tests_linux.gtk.x86
org.eclipse.jdt.debug.tests_macosx.carbon.ppc
org.eclipse.releng.tests_linux.gtk.x86
org.eclipse.releng.tests_linux.gtk.x86_5.0
org.eclipse.releng.tests_win32.win32.x86
HTTP Download:
http://download.eclipse.org/eclipse/downloads/drops/I20060602-0010
FTP Download:
user: anonymous
password: (e-mail address or leave blank)
server: download.eclipse.org
cd to directory: I20060602-0010
or
ftp://download.eclipse.org/I20060602-0010
_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev
### Eclipse Workspace Patch 1.0
#P org.eclipse.pde.doc.user
Index: guide/tools/launchers/tracing.htm
===================================================================
RCS file: /cvsroot/eclipse/org.eclipse.pde.doc.user/guide/tools/launchers/tracing.htm,v
retrieving revision 1.2
diff -u -r1.2 tracing.htm
--- guide/tools/launchers/tracing.htm 1 Jun 2006 19:39:31 -0000 1.2
+++ guide/tools/launchers/tracing.htm 2 Jun 2006 16:42:43 -0000
@@ -38,7 +38,7 @@
<li><em>org.eclipse.ui.ide/debug/gc</em> = <em>true</em></li>
<li><em>org.eclipse.ui.ide/debug/internalerror/openDialog</em> = <em>true</em> </li>
</ul>
-<p>In your code, to check if your plug-in is in debug mode (i.e. state of the master switch), you can check the return value of <span class="style4"><Activator>.isDebugging()</span>, where <span class="style4"><Activator></span> is the class specified in the <strong>Bundle-Activator</strong> header of your plug-in‘s <em>MANIFEST.MF </em>.</p>
+<p>In your code, to check if your plug-in is in debug mode (i.e. state of the master switch), you can check the return value of <span class="style4"><Activator>.isDebugging()</span>, where <span class="style4"><Activator></span> is the class specified in the <strong>Bundle-Activator</strong> header of your plug-in's <em>MANIFEST.MF </em>.</p>
<p>Values for individual flag names can be obtained by calling <span class="style4">Platform.getDebugOption(optionName)</span>.</p>
<p> </p>
<p class="style2">Enable Tracing </p>
Index: guide/tools/launchers/junit_main.htm
===================================================================
RCS file: /cvsroot/eclipse/org.eclipse.pde.doc.user/guide/tools/launchers/junit_main.htm,v
retrieving revision 1.2
diff -u -r1.2 junit_main.htm
--- guide/tools/launchers/junit_main.htm 1 Jun 2006 19:39:31 -0000 1.2
+++ guide/tools/launchers/junit_main.htm 2 Jun 2006 16:42:43 -0000
@@ -33,7 +33,7 @@
<p> </p>
<p class="style2">Program To Run</p>
<p>The <strong>Program to Run</strong> section is where you specify the product or application to test. </p>
-<p>The product combo box is populated with the IDs of all products (<em>org.eclipse.core.runtime.products</em> extensions) defined in the workspace and target plug-ins. The product ID that is initially selected is the default product as specified by the <strong>eclipse.product</strong> key in the <em>config.ini</em> file located in the <em><em>${target_home}/configuration</em></em> directory. The <em>${target_home}</em> variable refers to the location of the target platform as specified on the <strong>Windows > Preferences... > Plug-in Development > Target Platform</strong> preference page. In the Eclipse SDK, the default product ID is <em>org.eclipse.sdk.ide</em>.</p>
+<p>The product combo box is populated with the IDs of all products (<em>org.eclipse.core.runtime.products</em> extensions) defined in the workspace and target plug-ins. The product ID that is initially selected is the default product as specified by the <strong>eclipse.product</strong> key in the <em>config.ini</em> file located in the <em>${target_home}/configuration</em> directory. The <em>${target_home}</em> variable refers to the location of the target platform as specified on the <strong>Windows > Preferences... > Plug-in Development > Target Platform</strong> preference page. In the Eclipse SDK, the default product ID is <em>org.eclipse.sdk.ide</em>.</p>
<p>The application combo box is populated with the IDs of all applications (<em>org.eclipse.core.runtime.applications</em> extensions) defined in the workspace and target plug-ins. The application ID that is initially selected is the default application as specified by the <strong>eclipse.application</strong> key in the <em>config.ini</em> file that is located in the <em>${target_home}/configuration directory</em>. In the Eclipse SDK, the default application ID is <em>org.eclipse.ui.ide.workbench</em>. </p>
<p>Some tests neither require a user interface nor a workbench and can therefore be run in headless mode. The <em>JUnit Plug-in Test</em> launcher provides such a mode in the application combo box.</p>
<p><img src="../../images/launchers/launcher_junit_headless.PNG" alt="headless" hspace="30"> </p>
Index: guide/tools/launchers/configuration.htm
===================================================================
RCS file: /cvsroot/eclipse/org.eclipse.pde.doc.user/guide/tools/launchers/configuration.htm,v
retrieving revision 1.2
diff -u -r1.2 configuration.htm
--- guide/tools/launchers/configuration.htm 1 Jun 2006 19:39:31 -0000 1.2
+++ guide/tools/launchers/configuration.htm 2 Jun 2006 16:42:43 -0000
@@ -41,7 +41,7 @@
<li><strong>osgi.install.area</strong> - specifies the location of the target platform. </li>
<li><strong>osgi.splashPath</strong> - specifies one or more locations of the splash screen.</li>
</ul>
-<p>The <strong>Use an existing <em>config.ini</em> file as a template</strong> option takes an existing <em>config.ini</em> file and makes a copy of it. PDE neither adds nor removes properties from this file. However, PDE modifies the <strong>osgi.bundles</strong> and <strong>osgi.splashPath</strong> keys by substituting their generic bundle URL values with absolute paths that reflect the bundles’ actual disk locations.</p>
+<p>The <strong>Use an existing <em>config.ini</em> file as a template</strong> option takes an existing <em>config.ini</em> file and makes a copy of it. PDE neither adds nor removes properties from this file. However, PDE modifies the <strong>osgi.bundles</strong> and <strong>osgi.splashPath</strong> keys by substituting their generic bundle URL values with absolute paths that reflect the bundles' actual disk locations.</p>
<br>
<br>
<br>
Index: guide/tools/launchers/eclipse_application_launcher.htm
===================================================================
RCS file: /cvsroot/eclipse/org.eclipse.pde.doc.user/guide/tools/launchers/eclipse_application_launcher.htm,v
retrieving revision 1.2
diff -u -r1.2 eclipse_application_launcher.htm
--- guide/tools/launchers/eclipse_application_launcher.htm 1 Jun 2006 19:39:31 -0000 1.2
+++ guide/tools/launchers/eclipse_application_launcher.htm 2 Jun 2006 16:42:43 -0000
@@ -26,7 +26,7 @@
<p class="style2">Launching via a Shortcut</p>
<p>A quick way to test a plug-in is by launching a separate application via <strong>Eclipse Application</strong> launch shortcuts that are available as: </p>
<ul>
- <li> hot links in the <a href="../editors/manifest_editor/testing.htm">Testing</a> section of the plug-in manifest editor‘s <strong>Overview</strong> page</li>
+ <li> hot links in the <a href="../editors/manifest_editor/testing.htm">Testing</a> section of the plug-in manifest editor's <strong>Overview</strong> page</li>
<li>actions in the <strong>Run As > </strong>and <strong>Debug As ></strong> context menus of plug-in projects </li>
</ul>
<p>Launch shortcuts are context-sensitive. If the selected resource is a plug-in project or plug-in manifest editor that declares an application (an <em>org.eclipse.core.runtime.applications</em> extension) or a product (an <em>org.eclipse.core.runtime.products</em> extension), then PDE launches that application or product. The set of plug-ins PDE launches with is a minimal set made up of the selected plug-in and all its pre-requisites only. If the selected plug-in contains both a product extension and an application extension, the product extension takes precedence. </p>
Index: guide/tools/launchers/junit_configuration.htm
===================================================================
RCS file: /cvsroot/eclipse/org.eclipse.pde.doc.user/guide/tools/launchers/junit_configuration.htm,v
retrieving revision 1.2
diff -u -r1.2 junit_configuration.htm
--- guide/tools/launchers/junit_configuration.htm 1 Jun 2006 19:39:31 -0000 1.2
+++ guide/tools/launchers/junit_configuration.htm 2 Jun 2006 16:42:43 -0000
@@ -41,7 +41,7 @@
<li><strong>osgi.install.area</strong> - specifies the location of the target platform. </li>
<li><strong>osgi.splashPath</strong> - specifies one or more locations of the splash screen.</li>
</ul>
-<p>The <strong>Use an existing config.ini file as a template</strong> option takes an existing <em>config.ini</em> and makes a copy of it. PDE neither adds nor removes any properties from the file. However, PDE modifies the <strong>osgi.bundles</strong> and <strong>osgi.splashPath</strong> keys by substituting their generic bundle URL values with absolute paths that reflect the bundles’ actual disk locations.</p>
+<p>The <strong>Use an existing config.ini file as a template</strong> option takes an existing <em>config.ini</em> and makes a copy of it. PDE neither adds nor removes any properties from the file. However, PDE modifies the <strong>osgi.bundles</strong> and <strong>osgi.splashPath</strong> keys by substituting their generic bundle URL values with absolute paths that reflect the bundles' actual disk locations.</p>
<br>
<br>
<br>
Index: about.html
===================================================================
RCS file: /cvsroot/eclipse/org.eclipse.pde.doc.user/about.html,v
retrieving revision 1.16
diff -u -r1.16 about.html
--- about.html 1 Jun 2006 17:53:36 -0000 1.16
+++ about.html 2 Jun 2006 16:42:43 -0000
@@ -1,27 +1,28 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3c.org/TR/1999/REC-html401-19991224/loose.dtd";>
-<!-- saved from url=(0043)http://www.eclipse.org/legal/epl/about.html -->
-<HTML xmlns="http://www.w3.org/1999/xhtml";><HEAD><TITLE>About</TITLE><!-- ZoneLabs Privacy Insertion -->
-<SCRIPT language=javascript src="About_files/js"></SCRIPT>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
+<html xmlns="http://www.w3.org/1999/xhtml";>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
+<title>About</title>
+</head>
+<body lang="EN-US">
+<h2>About This Content</h2>
+
+<p>May 2, 2006</p>
+<h3>License</h3>
-<META http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
-<META content="MSHTML 6.00.2800.1543" name=GENERATOR></HEAD>
-<BODY lang=EN-US>
-<H2>About This Content</H2>
-<P>May 2, 2006</P>
-<H3>License</H3>
-<P>The Eclipse Foundation makes available all content in this plug-in
-("Content"). Unless otherwise indicated below, the Content is provided to you
-under the terms and conditions of the Eclipse Public License Version 1.0
-("EPL"). A copy of the EPL is available at <A
-href="http://www.eclipse.org/legal/epl-v10.html";>http://www.eclipse.org/legal/epl-v10.html</A>.
-For purposes of the EPL, "Program" will mean the Content.</P>
-<P>If you did not receive this Content directly from the Eclipse Foundation, the
-Content is being redistributed by another party ("Redistributor") and different
-terms and conditions may apply to your use of any object code in the Content.
-Check the Redistributor's license that was provided with the Content. If no such
-license exists, contact the Redistributor. Unless otherwise indicated below, the
-terms and conditions of the EPL still apply to any source code in the Content
-and such source code may be obtained at <A
-href="http://www.eclipse.org/";>http://www.eclipse.org/</A>.</P><!-- ZoneLabs Popup Blocking Insertion -->
-<SCRIPT language=javascript>postamble();</SCRIPT>
-</BODY></HTML>
+<p>The Eclipse Foundation makes available all content in this plug-in ("Content"). Unless otherwise
+indicated below, the Content is provided to you under the terms and conditions of the
+Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is available
+at <a href="http://www.eclipse.org/legal/epl-v10.html";>http://www.eclipse.org/legal/epl-v10.html</a>.
+For purposes of the EPL, "Program" will mean the Content.</p>
+
+<p>If you did not receive this Content directly from the Eclipse Foundation, the Content is
+being redistributed by another party ("Redistributor") and different terms and conditions may
+apply to your use of any object code in the Content. Check the Redistributor's license that was
+provided with the Content. If no such license exists, contact the Redistributor. Unless otherwise
+indicated below, the terms and conditions of the EPL still apply to any source code in the Content
+and such source code may be obtained at <a href="/">http://www.eclipse.org</a>.</p>
+
+</body>
+</html>
\ No newline at end of file
