Project Properties
To inspect or alter an EclipseME project properties, open the Properties dialog via the Project / Properties menu of the workbench.
Select the J2ME category from the left pane of the properties dialog. The project properties page for EclipseME looks like the following:
Property items:
| Item | Contents |
| J2ME Platform Definition |
The Platform Definition setting controls both which particular platform
the project is compiled against, and also affects the choice of devices
that are available in the Launch Configuration.
When this setting changes, the contents of your project are automatically recompiled. Thus, if you build a project using the MIDP 2.0 platform and then change to a MIDP 1.0 platform definition, your project may no longer compile because of references to classes, methods or constants not present in the MIDP 1.0 definition. |
| Sign project | Select this option to enable signing for this project. Note that, if you do this, you will, at minimum, need to specify a Keystore File and the appropriate Key Alias. |
| Keystore File | This setting specifies the keystore file that contains the private key used to sign the MIDlet suite and the certificate used to verify the signature. |
| Key Alias | The Key Alias identifies the particular key within the keystore that is to be used. |
| Prompt for password when required | If you select this option, EclipseME will prompt you for the keystore password and key password when it is time to retrieve information from the keystore. Note that EclipseME will then save this password information in memory so that you do not need to provide it again during this session with Eclipse. |
| Save passwords in workspace keyring | If you select this option, enter the keystore password and the key password in the spaces provided. EclipseME will save these passwords inside your keyring file. By default, this file is located in [workspace>]\.metadata\.plugins\org.eclipse.pde.core\eASEE\org.eclipse.core.runtime\.keyring, although you can specify a different file using Eclipse's -keyring command line argument. |
| Save passwords as part of project | If you select this option, enter the keystore password and the key password in the spaces provided. EclipseME will save these passwords in encrypted form in the .eclipseme file that is part of your project. |
| Crypto Provider | If you are using a non-standard cryptographic provider, such as the Bouncy Castle cryptographic libraries, place the provider ID in this area. If you are using the standard system provider, leave this space blank. |
| Keystore Type | If you are using a non-standard keystore format, such as the special format supported by Bouncy Castle, place the keystore format ID here. If you are using the standard system keystore type, leave this space blank. |
| Verify Settings | Pressing this button will cause EclipseME to attempt to retrieve the key and certificate from the keystore, and check it to make sure that it is of the correct type. If this test succeeds, the key should be suitable for MIDlet suite signing. If one or more of the parameters you have entered is incorrect, you will get an appropriate error message. It is generally advisable to make sure that the settings all verify before attempting to deploy a project with signing. |
For more information about MIDlet suite signing, click here.