mirrors/cdt
1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2025-08-03 14:25:37 +02:00
Code Issues Wiki Activity

[142968] getting rid of IBM strings

Browse source
This commit is contained in:
David McKnight 2006-12-07 19:19:44 +00:00
parent 930c30f06a
commit 4a9fb5a754
8 changed files with 109 additions and 214 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
rse/plugins/org.eclipse.rse.connectorservice.dstore/src/org/eclipse/rse/connectorservice/dstore/RexecDstoreServer.java
View file

@ -393,7 +393,7 @@ public class RexecDstoreServer implements IServerLauncher
* @return port number as String
*/
/*
* There used to be a problem in IBM Communications Server for z/OS and
* There used to be a problem in Communications Server for z/OS and
* the message from the REXEC daemon was in EBCDIC. see APAR PQ76782.
* Since this problem was fixed in Communication Server, there is no need to convert EBCDIC to ASCII
*/

6
rse/plugins/org.eclipse.rse.core/src/org/eclipse/rse/core/model/ISystemPreferenceChangeEvents.java
View file

@ -41,9 +41,5 @@ public interface ISystemPreferenceChangeEvents
* A connection type has been enabled or disabled
*/
public static final int EVENT_ENABLED_CONNECTIONS_CHANGED = 25;
/**
* The range 10000-10999 is reserved for IBM product use. We'll find a way to
* register these eventually.
*/
}

1
rse/plugins/org.eclipse.rse.logging/src/org/eclipse/rse/logging/performance/PerformanceLogger.java
View file

@ -85,7 +85,6 @@ import org.w3c.dom.Element;
public class PerformanceLogger {
public final static boolean _ENABLE_PERFORMANCE_LOGGING_IBM_INTERNAL_ = false;
public final static int OPTION_GET_ALL = 1;
public final static int OPTION_GET_FEATURE = 2;
public final static int OPTION_GET_VERSION = 3;

1
rse/plugins/org.eclipse.rse.subsystems.files.core/src/org/eclipse/rse/subsystems/files/core/model/ISystemFileTransferModeRegistry.java
View file

@ -28,7 +28,6 @@ public interface ISystemFileTransferModeRegistry extends ISystemFileTypes
// Default text file names
public static final String[] DEFAULT_TEXT_FILE_NAMES = {"application.xml", "build.properties", "fragment.xml",
"ibm-application-bnd.xmi", "ibm-application-ext.xmi",
"install.xml", "plugin.xml", "server-cfg.xml", "web.xml"};
// Default text file types

8
rse/plugins/org.eclipse.rse.ui/HelpContexts.xml
View file

@ -701,8 +701,8 @@ The list on the left shows the existing user actions:
The list on the left shows the existing named types:
- To <b>create</b> a new type, select the "New" node at the top of the list, enter information in the edit pane on the right, and press the <b>Create</b> button.
- To <b>edit</b> an existing type, select the type in the list, update the information in the edit pane on the right, and press the <b>Apply</b> button.
- To copy, paste, delete or re-order existing types, use the pop-up menu.
IBM-supplied types cannot be edited, but you can create a new type based on them by using copy and paste.
- To copy, paste, delete or re-order existing types, use the pop-up menu.
Supplied types cannot be edited, but you can create a new type based on them by using copy and paste.
</description></context>
<context id="wwnt0002"><description>Enter a comma-separated list of file extensions or file names. For file names that have no extension, such as "makefile", specify ".null" for the extension, as in "makefile.null".</description></context>
@ -717,7 +717,7 @@ IBM-supplied types cannot be edited, but you can create a new type based on them
<!-- USER DEFINED ACTIONS DIALOG ACTION: Move Down -->
<context id="udmd0000"><description>Move the selected action or type down in the list.</description></context>
<!-- USER DEFINED ACTIONS DIALOG ACTION: Restore Defaults -->
<context id="udrd0000"><description>Restore the action or type to its values as originally supplied by IBM.</description></context>
<context id="udrd0000"><description>Restore the action or type to its original values.</description></context>
<!-- WORK WITH COMPILE COMMANDS DIALOG... -->
<context id="wwcc0000"><description>Use this dialog to create or edit compile commands that appear in the Compile pop-up menu for remote resources. Each active profile can contain unique compile commands, and all applicable commands from all active profiles are shown in the Compile menu.
@ -738,7 +738,7 @@ The list on the left shows the existing compile commands:
<!-- WORK WITH COMPILE COMMANDS DIALOG ACTION: Move Down -->
<context id="wwcc5000"><description>Move the selected compile command down in the list.</description></context>
<!-- WORK WITH COMPILE COMMANDS DIALOG ACTION: Restore Defaults -->
<context id="wwcc6000"><description>Restore the compile command to its values as originally supplied by IBM.</description></context>
<context id="wwcc6000"><description>Restore the compile command to its original values.</description></context>
<!-- Save password dialogs -->
<context id="pwdi0000">

82
rse/plugins/org.eclipse.rse.ui/schema/popupMenus.exsd
View file

@ -198,19 +198,7 @@ declared defined with the specified category.
&lt;p&gt;
This category can be scalar, or it can be generic to match on
multiple subsystem configuration categories. The
categories of the IBM-supplied subsystem factories that display
remote resources in the Remote
Systems view are:
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;files&lt;/b&gt;. For subsystems that list hierarchical file
system resources, such as folders and files.
&lt;li&gt;&lt;b&gt;nativefiles&lt;/b&gt;. For subsystems that list non-hierarchical file
system resources, such as in the iSeries QSYS file system.
&lt;li&gt;&lt;b&gt;commands&lt;/b&gt;. For subsystems that list remote commands.
&lt;li&gt;&lt;b&gt;jobs&lt;/b&gt;. For subsystems that list remote jobs.
&lt;/ul&gt;
multiple subsystem configuration categories.
&lt;br&gt;
</documentation>
</annotation>
@ -255,28 +243,7 @@ Specify as many of these optional filters like this as needed to explicitly scop
This filter specifies a type category. Normally the subsystemconfigurationid
is sufficient, but some subsystems display multiple types of
resources, and these are categorized by a type name that can
be used to scope property pages. Here are the type categories supported by IBM-
supplied subsystems:
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;files&lt;/b&gt;. For hierarchical file systems resources.
&lt;li&gt;&lt;b&gt;commands&lt;/b&gt;. For remote commands.
&lt;li&gt;&lt;b&gt;jobs&lt;/b&gt;. For remote jobs.
&lt;/ul&gt;
&lt;br&gt;
The IBM-supplied subsystem for iSeries native file system objects also supports
these type categories:
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;LIBRARIES&lt;/b&gt;. Set for libraries.
&lt;li&gt;&lt;b&gt;OBJECTS&lt;/b&gt;. Set for objects, excluding files.
&lt;li&gt;&lt;b&gt;OBJECTFILES&lt;/b&gt;. Set for file objects. Use &lt;samp&gt;OBJECTS*&lt;/samp&gt;
to match on all objects.
&lt;li&gt;&lt;b&gt;MEMBERS&lt;/b&gt;. Set for data and source file members.
&lt;li&gt;&lt;b&gt;RECORDS&lt;/b&gt;. Set for record formats within files.
&lt;li&gt;&lt;b&gt;FIELDS&lt;/b&gt;. Set for fields within record formats.
&lt;li&gt;&lt;b&gt;MESSAGE_DESCRIPTIONS&lt;/b&gt;. Set for messages within message
files.
&lt;/ul&gt;
be used to scope property pages.
&lt;br&gt;
</documentation>
</annotation>
@ -291,18 +258,7 @@ all the actions defined in this objectContribution element.
&lt;p&gt;
This filter specifies a resource type, either simple or generic.
The resource types depends on the subsystem. The types
for IBM-supplied subsystems which support them are:
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;filesXXX&lt;/b&gt;. Either &lt;i&gt;folder&lt;/i&gt; or &lt;i&gt;file&lt;/i&gt;.
&lt;li&gt;&lt;b&gt;files400&lt;/b&gt;. This is the object&apos;s type (for objects),
such as &lt;i&gt;*PGM&lt;/i&gt;, or member&apos;s type (for members),
such as &lt;i&gt;RPGLE&lt;/i&gt;. Since * is a valid character in an iSeries
object type, use %ast. instead of * to prevent wildcard matching.
For example, to prevent matching on both *PGM and *SRVPGM, use %ast.PGM
for the type.
&lt;/ul&gt;
The resource types depends on the subsystem.
&lt;br&gt;
</documentation>
</annotation>
@ -318,16 +274,6 @@ all the actions defined in this objectContribution element.
&lt;p&gt;
This filter specifies a simple or generic resource subtype to
match. Not all subsystems support subtypes for their resources.
The IBM-supplied subsystems that do support this are:
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;FilesXXX. This can be either &lt;i&gt;subfolder&lt;/i&gt; for nested
folders only, or
&lt;i&gt;root&lt;/i&gt; for the root folder or Windows&apos; drives.
&lt;li&gt;Files400. For iSeries objects within a library, this is the
object&apos;s attribute. For members, it is either &lt;i&gt;DTA&lt;/i&gt; or &lt;i&gt;SRC&lt;/i&gt;.
For fields, it is the field&apos;s datatype (a single character).
&lt;/ul&gt;
&lt;br&gt;
</documentation>
</annotation>
@ -341,8 +287,7 @@ Specify as many of these optional filters like this as needed to explicitly scop
all the actions defined in this objectContribution element.
&lt;p&gt;
This filter specifies a simple or generic resource sub-subtype
to match. No IBM-supplied subsystems support sub-subtypes for
their resources today.
to match.
&lt;/p&gt;
</documentation>
</annotation>
@ -439,8 +384,8 @@ such as move up or move down.
&lt;/ul&gt;
&lt;p&gt;
You may also desire to place your action in an IBM-supplied cascading menu.
To do this, for the ID-part, specify one of the following IBM-supplied menu IDs:
You may also desire to place your action in an supplied cascading menu.
To do this, for the ID-part, specify one of the following supplied menu IDs:
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;&quot;menu.new&quot;&lt;/b&gt;. This is the cascading &quot;New-&gt;&quot; menu.
&lt;li&gt;&lt;b&gt;&quot;menu.goto&quot;&lt;/b&gt;. This is the cascading &quot;Goto-&gt;&quot; menu.
@ -454,7 +399,7 @@ To do this, for the ID-part, specify one of the following IBM-supplied menu IDs:
</documentation>
</annotation>
</attribute>
</complexType>
</complexType>
</element>
<element name="action">
@ -507,12 +452,12 @@ directory.
<documentation>
A slash-delimited path that is used to specify the location of the the action in the popup menu. Each token
in the path, except the last one, represents an existing submenu in the hierarchy, as defined via the &lt;samp&gt;id&lt;/samp&gt;
attribute of a &lt;samp&gt;menu&lt;/samp&gt; element previously defined. Alternatively, the ID of an IBM-supplied cascading
attribute of a &lt;samp&gt;menu&lt;/samp&gt; element previously defined. Alternatively, the ID of a supplied cascading
menu can be specified. The last token represents the named separator group into which the action will be added.
If no path is given, this must be an IBM-supplied group.
If no path is given, this must be a supplied group.
&lt;p&gt;
See the comments for the path attribute of the menu element for a list of the IBM-supplied cascading menus,
and IBM-supplied separator groups.
See the comments for the path attribute of the menu element for a list of the supplied cascading menus,
and supplied separator groups.
&lt;/p&gt;
&lt;p&gt;
If a path is given, then this must match the name attribute of a &lt;samp&gt;separator&lt;/samp&gt; sub-element
@ -562,7 +507,7 @@ F1 while the menu item is highlighted will display help for the given context ID
<annotation>
<documentation>
Your action class that implements &lt;samp&gt;org.eclipse.ui.IObjectActionDelegate&lt;/samp&gt;.
Typically you will extend one of the IBM-supplied classes, described in the API Information section.
Typically you will extend one of the supplied classes, described in the API Information section.
</documentation>
<appInfo>
<meta.attribute kind="java" basedOn="org.eclipse.ui.IObjectActionDelegate"/>
@ -724,8 +669,7 @@ are unrelated to each other:
&lt;/extension&gt;
&lt;/pre&gt;
&lt;/p&gt;
The following example shows how to place actions within an
IBM-supplied cascading menu:
The following example shows how to place actions within a supplied cascading menu:
&lt;h3&gt;Example Five&lt;/h3&gt;
&lt;p&gt;

51
rse/plugins/org.eclipse.rse.ui/schema/propertyPages.exsd
View file

@ -139,7 +139,7 @@ You can specify multiple values if you comma-separate them.
<annotation>
<documentation>
a fully qualified name of the class that implements &lt;code&gt;org.eclipse.ui.IWorkbenchPropertyPage&lt;/code&gt;.
Or better yet, extends one of the IBM-supplied base classes, described in the API Information section.
Or better yet, extends one of the supplied base classes, described in the API Information section.
</documentation>
<appInfo>
<meta.attribute kind="java" basedOn="org.eclipse.ui.IWorkbenchPropertyPage"/>
@ -242,28 +242,7 @@ Specify as many of these optional filters like this as needed to explicitly scop
This filter specifies a type category. Normally the subsystemconfigurationid
is sufficient, but some subsystems display multiple types of
resources, and these are categorized by a type name that can
be used to scope property pages. Here are the type categories supported by IBM-
supplied subsystems:
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;files&lt;/b&gt;. For hierarchical file systems resources.
&lt;li&gt;&lt;b&gt;commands&lt;/b&gt;. For remote commands.
&lt;li&gt;&lt;b&gt;jobs&lt;/b&gt;. For remote jobs.
&lt;/ul&gt;
&lt;br&gt;
The IBM-supplied subsystem for iSeries native file system objects also supports
these type categories:
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;LIBRARIES&lt;/b&gt;. Set for libraries.
&lt;li&gt;&lt;b&gt;OBJECTS&lt;/b&gt;. Set for objects, excluding files.
&lt;li&gt;&lt;b&gt;OBJECTFILES&lt;/b&gt;. Set for file objects. Use &lt;samp&gt;OBJECTS*&lt;/samp&gt;
to match on all objects.
&lt;li&gt;&lt;b&gt;MEMBERS&lt;/b&gt;. Set for data and source file members.
&lt;li&gt;&lt;b&gt;RECORDS&lt;/b&gt;. Set for record formats within files.
&lt;li&gt;&lt;b&gt;FIELDS&lt;/b&gt;. Set for fields within record formats.
&lt;li&gt;&lt;b&gt;MESSAGE_DESCRIPTIONS&lt;/b&gt;. Set for messages within message
files.
&lt;/ul&gt;
be used to scope property pages.
&lt;br&gt;
</documentation>
</annotation>
@ -278,18 +257,7 @@ this property page element.
&lt;p&gt;
This filter specifies a resource type, either simple or generic.
The resource types depends on the subsystem. The types
for IBM-supplied subsystems which support them are:
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;filesXXX&lt;/b&gt;. Either &lt;i&gt;folder&lt;/i&gt; or &lt;i&gt;file&lt;/i&gt;.
&lt;li&gt;&lt;b&gt;files400&lt;/b&gt;. This is the object&apos;s type (for objects),
such as &lt;i&gt;*PGM&lt;/i&gt;, or member&apos;s type (for members),
such as &lt;i&gt;RPGLE&lt;/i&gt;. Since * is a valid character in an iSeries
object type, use %ast. instead of * to prevent wildcard matching.
For example, to prevent matching on both *PGM and *SRVPGM, use %ast.PGM
for the type.
&lt;/ul&gt;
The resource types depends on the subsystem.
&lt;br&gt;
</documentation>
</annotation>
@ -305,16 +273,6 @@ this property page element.
&lt;p&gt;
This filter specifies a simple or generic resource subtype to
match. Not all subsystems support subtypes for their resources.
The IBM-supplied subsystems that do support this are:
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;FilesXXX. This can be either &lt;i&gt;subfolder&lt;/i&gt; for nested
folders only, or
&lt;i&gt;root&lt;/i&gt; for the root folder or Windows&apos; drives.
&lt;li&gt;Files400. For iSeries objects within a library, this is the
object&apos;s attribute. For members, this is either &lt;i&gt;DTA&lt;/i&gt; or &lt;i&gt;SRC&lt;/i&gt;.
For fields, this is the field&apos;s datatype (a single character).
&lt;/ul&gt;
&lt;br&gt;
</documentation>
</annotation>
@ -329,8 +287,7 @@ this property page element.
&lt;p&gt;
This filter specifies a simple or generic resource sub-subtype
to match. No IBM-supplied subsystems support sub-subtypes for
their resources today.
to match.
&lt;/p&gt;
</documentation>
</annotation>

172
rse/tests/org.eclipse.rse.tests/test.xml
View file

@ -1,86 +1,86 @@
<?xml version="1.0"?>
<!--
Run post build tests.
Not yet complete.
Needs to be updated and tested for org.eclipse.rse
-->
<project name="testsuite" default="run" basedir=".">
<!-- The property ${eclipse-home} should be passed into this script -->
<!-- Set a meaningful default value for when it is not. -->
<property name="eclipse-home" value="${basedir}\..\.."/>
<!-- sets the properties eclipse-home, and library-file -->
<property name="plugin-name" value="org.eclipse.rse.tests"/>
<property name="library-file" value="${eclipse-home}/plugins/org.eclipse.test/library.xml"/>
<!-- This target holds all initialization code that needs to be done for -->
<!-- all tests that are to be run. Initialization for individual tests -->
<!-- should be done within the body of the suite target. -->
<target name="init">
<tstamp/>
<delete>
<fileset dir="${eclipse-home}" includes="org.eclipse.rse.tests.*.xml"/>
</delete>
</target>
<!-- This target defines the tests that need to be run. -->
<target name="suite">
<property name="test-folder" value="${eclipse-home}/ui_iseriestests_folder"/>
<delete dir="${test-folder}" quiet="true"/>
<ant target="ui-test" antfile="${library-file}" dir="${eclipse-home}">
<property name="data-dir" value="${test-folder}"/>
<property name="plugin-name" value="${plugin-name}"/>
<property name="classname" value="org.eclipse.rse.tests.SampleTestSuite"/>
</ant>
<!-- Commented out until source of problem found (not reusing same workspace dir)
<ant target="ui-test" antfile="${library-file}" dir="${eclipse-home}">
<property name="data-dir" value="${session-folder}"/>
<property name="plugin-name" value="${plugin-name}"/>
<property name="classname"
value="org.eclipse.ui.tests.api.SessionRestoreTest"/>
</ant>
-->
<!--
<property name="sniff-folder"
value="${eclipse-home}/ui_sniff_folder"/>
<delete dir="${sniff-folder}" quiet="true"/>
<ant target="ui-test" antfile="${library-file}" dir="${eclipse-home}">
<property name="data-dir" value="${sniff-folder}"/>
<property name="plugin-name" value="${plugin-name}"/>
<property name="classname"
value="org.eclipse.ui.tests.UiTestSuite"/>
</ant>
<property name="jface-sniff-folder"
value="${eclipse-home}/jface_sniff_folder"/>
<delete dir="${jface-sniff-folder}" quiet="true"/>
<ant target="core-test" antfile="${library-file}" dir="${eclipse-home}">
<property name="data-dir" value="${jface-sniff-folder}"/>
<property name="plugin-name" value="${plugin-name}"/>
<property name="classname"
value="org.eclipse.jface.tests.viewers.AllTests"/>
</ant>
-->
</target>
<!-- This target holds code to cleanup the testing environment after -->
<!-- after all of the tests have been run. You can use this target to -->
<!-- delete temporary files that have been created. -->
<target name="cleanup">
</target>
<!-- This target runs the test suite. Any actions that need to happen -->
<!-- after all the tests have been run should go here. -->
<target name="run" depends="init,suite,cleanup">
<ant target="collect" antfile="${library-file}" dir="${eclipse-home}">
<property name="includes" value="com.ibm.etools.iseries.*.xml"/>
<property name="output-file" value="${plugin-name}.xml"/>
</ant>
</target>
</project>
<?xml version="1.0"?>
<!--
Run post build tests.
Not yet complete.
Needs to be updated and tested for org.eclipse.rse
-->
<project name="testsuite" default="run" basedir=".">
<!-- The property ${eclipse-home} should be passed into this script -->
<!-- Set a meaningful default value for when it is not. -->
<property name="eclipse-home" value="${basedir}\..\.."/>
<!-- sets the properties eclipse-home, and library-file -->
<property name="plugin-name" value="org.eclipse.rse.tests"/>
<property name="library-file" value="${eclipse-home}/plugins/org.eclipse.test/library.xml"/>
<!-- This target holds all initialization code that needs to be done for -->
<!-- all tests that are to be run. Initialization for individual tests -->
<!-- should be done within the body of the suite target. -->
<target name="init">
<tstamp/>
<delete>
<fileset dir="${eclipse-home}" includes="org.eclipse.rse.tests.*.xml"/>
</delete>
</target>
<!-- This target defines the tests that need to be run. -->
<target name="suite">
<property name="test-folder" value="${eclipse-home}/ui_iseriestests_folder"/>
<delete dir="${test-folder}" quiet="true"/>
<ant target="ui-test" antfile="${library-file}" dir="${eclipse-home}">
<property name="data-dir" value="${test-folder}"/>
<property name="plugin-name" value="${plugin-name}"/>
<property name="classname" value="org.eclipse.rse.tests.SampleTestSuite"/>
</ant>
<!-- Commented out until source of problem found (not reusing same workspace dir)
<ant target="ui-test" antfile="${library-file}" dir="${eclipse-home}">
<property name="data-dir" value="${session-folder}"/>
<property name="plugin-name" value="${plugin-name}"/>
<property name="classname"
value="org.eclipse.ui.tests.api.SessionRestoreTest"/>
</ant>
-->
<!--
<property name="sniff-folder"
value="${eclipse-home}/ui_sniff_folder"/>
<delete dir="${sniff-folder}" quiet="true"/>
<ant target="ui-test" antfile="${library-file}" dir="${eclipse-home}">
<property name="data-dir" value="${sniff-folder}"/>
<property name="plugin-name" value="${plugin-name}"/>
<property name="classname"
value="org.eclipse.ui.tests.UiTestSuite"/>
</ant>
<property name="jface-sniff-folder"
value="${eclipse-home}/jface_sniff_folder"/>
<delete dir="${jface-sniff-folder}" quiet="true"/>
<ant target="core-test" antfile="${library-file}" dir="${eclipse-home}">
<property name="data-dir" value="${jface-sniff-folder}"/>
<property name="plugin-name" value="${plugin-name}"/>
<property name="classname"
value="org.eclipse.jface.tests.viewers.AllTests"/>
</ant>
-->
</target>
<!-- This target holds code to cleanup the testing environment after -->
<!-- after all of the tests have been run. You can use this target to -->
<!-- delete temporary files that have been created. -->
<target name="cleanup">
</target>
<!-- This target runs the test suite. Any actions that need to happen -->
<!-- after all the tests have been run should go here. -->
<target name="run" depends="init,suite,cleanup">
<ant target="collect" antfile="${library-file}" dir="${eclipse-home}">
<property name="includes" value="org.eclipse.rse.*.xml"/>
<property name="output-file" value="${plugin-name}.xml"/>
</ant>
</target>
</project>