Run/Debug Configuration: J2ME
J2ME run/debug configuration options vary depending on the SDK you are using to develop your mobile applications.
This section describes the options that are specific for WTK and DoJa, as well as the general options that apply to both SDKs.
This section provides descriptions of the configuration-specific items,
as well as the toolbar and options that are common for all run/debug configurations.
|Name||In this text box, specify the name of the current run/debug configuration.|
|Jad/Class/OTA||Select, which of the following sources - Jad, MIDlet class or OTA - is used to be run/debugged.
Each source has its own settings described below. |
|JAD||If you have selected to use Jad file as the source for running and debugging,
you need only to specify its location in the Jad File.
|Class Settings||If you have selected to use MIDlet class as the source for running and debugging, specify the following options:
MIDlet Class: Specify here the MIDlet class to run/debug.
User Defined Settings: Use this options group
to view/introduce/delete/move MIDlet class settings defined by the user.
These options can be set, if you have selected to use OTA as the source for running and debugging.
This functionality emulates wireless download of the software from the server.
Therefore, it is necessary to have a working server with such service and the necessary suite (which you want to install and launch) on it.
This service is completely dependent on the emulator vendor and IntelliJ IDEA does not provide it.
So, it should be provided by the emulator or separately by the emulator vendor (for instance, like Nokia does).
Thus, you need to have three items ready - a server, a service and tested suite on that server.
Remember that the actual options list varies from emulator type.
Install from URL: Specify the URL from which the necessary suite can be downloaded. Later on, this suite is installed on the emulator.
Force installation: Select this option to reinstall the suite, if it is already installed.
Install, run and remove: The suite is installed on the emulator, launched and removed afterwards.
Run/Remove previously installed: The previously installed suites are run or removed, respectively.
Update Suites: Click this button to update the list of suites present on the server.
|Jam/Class||Select which of the files, Jam or IApplication Class, is to be run/debugged. |
If you have selected to use Jam file as the source for running and debugging,
you need only to specify its location in the Jam File field.|
If you want to use IApplication Class as source for running/debugging,
specify its location in the IApplication Class field.|
|Device||Select one of the available devices for the current emulator.|
|Open Preferences||Opens the emulator's Preferences dialog. For more information, refer to emulator's documentation.|
|Open Utils||Opens the emulator's Utilities dialog. For more information, refer to emulator's documentation.|
|Emulator parameters||Type in/edit emulator parameters such as |
-mx heap_size or
|Use classpath and JDK of module||Select a mobile module from the list of modules configured in your project. The classpath and JDK of
this module will be used to run your J2ME module with the current run configuration.
|Name||In this text box, specify the name of the current run/debug configuration. This field does not appear for the default run/debug configurations.|
This node in the left-hand pane of the dialog box contains the default run/debug configuration settings.
Select the desired configuration to change its default settings in the right-hand pane.
The defaults are applied to all newly created run/debug configurations.
Select this check box to make the run/debug configuration available to other team members.
If the directory-based project format is used,
the settings for a run/debug configuration are stored in a separate .xml file in the
if the run/debug configuration is shared, or in the
.idea\workspace.xml file otherwise.
If the file-based format is used,
the settings are stored in the
.ipr file for shared configurations, or
.iws file otherwise.
This check box is not available when editing the run/debug configuration defaults.
|Single instance only||If this check box is selected, this run/debug configuration cannot be launched more than once.
Every time a new run/debug configuration is launched, IntelliJ IDEA checks the presence of the other instances
of the same run/debug configuration, and displays a confirmation dialog box. If you click OK
in the confirmation dialog box, the first instance of the runner will be stopped,
and the next one will take its place.
This makes sense when the usage of certain resources can cause conflicts, or when launching two run/debug
configurations of the same type consumes too much of the CPU and memory resources.
If this check box is not selected, it is possible to launch as many instances of the runner as required.
So doing, each runner will start in its own tab of the Run tool window.
|Before launch||Specify which tasks must be performed before applying the run/debug configuration.
The specified tasks are performed in the order they appear in the list.
||Click this icon to add a task to the list. Select the task to be added:
Run External tool.
Select this option to run an application which is external to IntelliJ IDEA.
In the dialog that opens, select the application or applications that should be run.
If the necessary application is not defined in IntelliJ IDEA yet, add its definition.
For more information, see Configuring Third-Party Tools and External Tools.
Select this option to have the project or module compiled.
The Make Module command will be carried out if a particular module is specified in the run/debug configuration, and
the Make Project command otherwise.
If an error occurs during the compilation,
IntelliJ IDEA won't attempt to start the run/debug configuration.
Make, no error check.
The same as the Make option but IntelliJ IDEA will try to start the run/debug configuration
irrespective of the compilation result.
Select this option to have an artifact or artifacts built.
In the dialog that opens, select the artifact or artifacts that should be built.
See also, Configuring Artifacts.
Run Another Configuration.
Select this option to have another run/debug configuration executed.
In the dialog that opens, select the configuration to run.
This option is available only if you have already at least one run/debug configuration in the current project.
Run Ant target.
Select this option to have an Ant target run.
In the dialog that opens, select the target to be run.
For more information, see Ant.
Generate CoffeeScript Source Maps.
Select this option to have the source maps for your CoffeeScript sources generated.
In the dialog that opens, specify where your CoffeeScript source files are located.
For more information, see CoffeeScript Support.
Run Maven Goal.
Select this option to have a Maven goal run.
In the dialog that opens, select the goal to be run.
For more information, see Maven.
Run Remote External tool: Add a remote SSH external tool. Refer to the section Remote SSH External Tools for details.
||Click this icon to remove the selected task from the list.|
||Click this icon to edit the selected task.
Make the necessary changes in the dialog that opens.|
Click this icon to move the selected task one line up in the list.|
Click this icon to move the selected task one line down in the list.|
|Show this page||
Select this check box to have the run/debug configuration settings shown prior to
actually starting the run/debug configuration.|
|Active tool window||Select this option if you want the Run/Debug tool windows
to be activated automatically when you run/debug your application. This option is enabled by default.|
Last modified: 13 July 2016