> 11.3.2 | Eclipse 3.0 and Eclipse 3.1

> We recommend that Eclipse 3.0.1 or higher is to be used.

> 11.3.2.1 | Eclipse 3.0

> Please use the customized Eclipse ME Plugin version that is distributed with the SMTK CD under the directory “EclipseMEplugin_WM” only for Eclipse 3.0.1 and 3.0.2 and install Eclipse ME as described in Section 3.4. However, instead of selecting "eclipseme.feature_1. 2.3_site.zip" choose “\EclipseMEpluging_WM\plugin.zip”1 from SMTK CD after clicking the New Archived Site… button.

> 11.3.2.2 | Eclipse 3.1

> If Eclipse is not installed, please follow the steps as described in Section 3.4.
> Please use and install EclipseME plugin 1.2.1, 1.2.3 or 1.5.x for Eclipse 3.1.0, 3.1.1 or 3.1.2.

> 11.3.2.3 | Eclipse 3.2

> If Eclipse is not installed, please follow the steps as described in Section 3.4.
> Please use and install EclipseME plugin 1.5.5 or 1.6.8.
> It is recommended to use Eclipse 3.2.2 with ME 1.5.5 for working with Java Debugging session.

> 11.3.2.4 | Using Eclipse with ME Plugin up to Version 1.2.3

> 11.3.2.4.1 | Additional Configuration of Integrated Emulator

> The following configuration is displayed after SMTK integration into Eclipse by using the Eclipse menu Windows → Preferences → J2ME → Platform Components:
> Figure 38: Eclipse – Display of different integrated emulators
> To use the debugger it is necessary to increase the debug server delay timeout of Eclipse IDE. Please set the timeout under Windows → Preferences → J2ME → Debug Server Delay to 25000. If you develop an extremely large application you may have to increase this timeout.

> 11.3.2.4.2 | Switching Emulators

> You can easily switch between different installed emulators by using the preferences of a project and choosing e.g. Siemens IMP-NG TC65 R2 Module, see figure below.
> Figure 39: Eclipse – J2ME platform

> 11.3.2.5 | Using Eclipse with ME Plugin 1.5.x

> Eclipse ME Plugin 1.5.x is supported by the TC65, XT65/XT75 and AC65/AC75 CDs. This Eclipse ME Plugin is using a completely new device management concept to integrate different emulators. The integration and disintegration of the TC65 resp. XT65/XT75 or AC65/AC75 emulator is only automatically possible by using the TC65 resp. XT65/XT75 or AC65/AC75 SMTK CD!
> Please note that selecting the TC65 resp. XT65/XT75 or AC65/AC75 emulator by using the Eclipse menu Window → Preferences → J2ME → Device Management → Import and browsing to the respective emulator directory will not integrate the emulator.
> Note: Manual emulator integration (by using Eclipse menu) is supported by Eclipse with using ME Plugin 1.5.5 and later. Automatic emulator integration using SMTK CD is possible for all Eclipse ME Plugin 1.5.x.

> 11.3.2.5.1 | Additional Configuration of Integrated Emulator

> The following configuration is displayed after SMTK integration into Eclipse by using the Eclipse menu Windows → Preferences → J2ME → Device Management:
> Figure 40: Eclipse with ME Plugin 1.5.0 – Display of different integrated emulators
> To use the debugger it is necessary to increase the debug server delay timeout of Eclipse IDE. Please set the timeout under Windows → Preferences → J2ME → Debug Server Delay to 25000. If you develop an extremely large application you may have to increase this timeout.

> 11.3.2.5.2 | Switching Emulators

> You can easily switch between different installed emulators by using the properties of a project and choosing a Device Group, e.g. "Siemens IMP-NG XT75 Wireless Toolkit". You can select a device also by using the Manage Devices… button, see figure below.
> Figure 41: Eclipse with ME Plugin 1.5.0 – J2ME platform

> 11.3.2.6 | Using Eclipse with ME Plugin 1.6.x

> Automatic integration into Eclipse ME Plugin 1.6.x is supported by using the TC65 CD. All configurations, settings and using the Eclipse IDE are done in a very similar way as for Eclipse ME Plugin 1.5.x and are described in the Section 11.3.2.5.1 and Section 11.3.2.5.2.

> 11.3.2.7 | Import Example

> You can import an existing Eclipse project using the following steps:

> - | Open menu: File → Import → Existing Project into Workspace

> - | Choose the root directory of the Eclipse project (e.g. “Hello World” example of the SMTK CD). See figure below.

> Figure 42: Eclipse – Project import
> The following figure shows the “Hello World” example in the IDE.
> Figure 43: Eclipse - Example
> The html help files of the SMTK can be accessed directly by pressing Shift+F2 while the cursor points to a Java expression in a Java source file.

> 11.3.2.8 | Compile and Debug

> To build the jar and jad files you have rebuild the project with the Create Package function. Open the context menu of the project and go to J2ME → Create Package.
> Figure 44: Eclipse – Create package
> Now you are ready to debug your project. Run → Debug…
> An emulator launcher with pre-settings is provided for starting the debugging session.
> Please ensure that you have selected the right project and executable midlet.
> Note: Before starting Java debugging session with the HelloWorld-Sample it is recommended to check the setting of used emulator (e.g. TC65_R3 emulator in project properties see Section 11.3.2.5.2), to clean the project with configuration "automatically build" (using Eclipse menu Project → Clean…) and to compile it completely (using project’s context menu of the "HelloWorld" project select J2ME → Create Package).
> Reason: Eclipse is storing internally old settings for an old used "HelloWorld-Sample", if you have used Eclipse with "HelloWorld-Sample" for another IMP-NG product before!
> Figure 45: Eclipse - Configuration
> Restriction:
> The integration of the SMTK using the SMTK installer depends selecting the offered default workspace “\workspace” of Eclipse (e.g. Eclipse 3.0.1 and 3.0.2 “..\eclipse\workspace\..” or Eclipse 3.1.0, 3.1.1 and 3.1.2 “..\Documents and Settings\<user name>\workspace\..”).
> If you like to use the SMTK integration inside other workspaces, please integrate SMTK manually in these workspaces using Eclipse menu Window → Preferences → J2ME → Platform Components (as shown in Figure 36). Please keep in mind that all manually integrated SMTKs have to be removed manually as well in case of removing SMTK.
> Note for using Eclipse 3.2.2 ME 1.6.8:
> Start debugging using "TC65 Rel.3 emulator" please select in "Midlet" the "HelloWorld" Midlet sample from the list of Midlets. The project name will be selected automatically.
> Remarks using Eclipse under Windows Vista (only supported for TC65):
> The Eclipse workspace directory differs from the location used under Windows 2000 and Windows XP. Using Windows Vista the following loaction is used for automatic integration of TC65 into Eclipse:
> "<drive name>:\Users\<your login>\AppData\workspace"
> (e.g. "c:\Users\<your login>\AppData\workspace")
> Please select this workspace before starting Java debugging with Eclipse!

> 11.3.2.9 | Starting Debug Session without Downloading Java Files

> It is possible to start a debugging session without download of the Java files (*.jad and *.jar) again. The emulator has to be started with an additional parameter “-noload” and downloading of the Java files is suppressed. Please add the parameter in the following emulator configuration line as described in the figure:
> Figure 46: Eclipse - Configuration
> Please keep in mind that you have to remove this emulator option before starting debugging session with download of Java files. The Java files are not updated in the Flash files system of the module while option “-noload” is set!
> Note for Eclipse 3.2.2 ME 1.6.8:
> The option "-noload" does not take previously set breakpoints into account. In other words, if you have set breakpoints in your Java source file and would like to start the debugging session with the "-noload" parameter, no previous set breakpoint is reached.
> Please use Eclipse 3.2.2 ME 1.5.5 for starting debugging session with "-noload" parameter.
> Note for using Eclipse 3.2.x ME 1.5.x and 1.6.x:
> During debugging it is sometimes possible, that if a breakpoint is reached, the Java program stops, but no breakpoint is indicated in the Java source line (Java source windows). In this case please select the Java Thread in the "Debug" window and select "System Thread" where the hit breakpoint is shown. The corresponding source line is highlighted inside the Java source windows (e.g. "HelloWorld.java") as well for the hit breakpoint. See the following figure.
> Figure 47: Eclipse 3.2.x ME1.5.x and 1.6.x select System Java Thread for showing breakpoint line in Java source

> 1
> Eclipse WM Plugin is not included anymore on TC65 CD