New Client Services Fragment Project WizardAdded by IBM on October 4, 2010 | Version 1 (Original)
|This wizard allows you to create a new Client Services fragment project.
This wizard allows you to create a new Client Services fragment project.
This wizard can be accessed as follows:
- Select File > New > Project. The new project wizard displays.
- Expand the Client Services folder and select Client Services Fragment Project.
Refer to the following tables for a description of the options and their default values.
Table 1. Client Services Fragment Project page
|Project name||Enter a name for your new Client Services fragment project.||None|
|Project Contents||You may deselect "Use default" and click Browse to select a file system location for your new Client Services Fragment Project.||The "Use default location" creates the project in your current workspace|
|Create a Java project ||Select this if the project will contain Java code. Deselect this if the project will only contain non-Java resources. ||Selected to create a Java project.|
|Source Folder Name ||Folder name for Java source files. ||src|
|Output Folder Name||Folder name for Java class files.||bin|
This is followed by the Fragment Content page:
Table 2. Fragment Content page
|Fragment ID ||This is a unique bundle symbolic name. It is suggested that you update this from the default value. The bundle name should be a unique URI, following the Java package naming conventions. ||The project name is used as the default value. |
|Fragment Version ||The fragment version. The version is in the form of major, minor, and micro numbers, separated by ‘.’. ||1.0.0 |
|Fragment Name ||A descriptive bundle name. ||The default name is constructed by appending “Fragment” to the project name. |
|Fragment Provider ||A description of the fragment provider. ||None |
|Class path ||The name of the JAR file in which the project’s built contents will be placed. ||The project name is used as the JAR file based name. |
|Plug-in ID||Specify the ID, version, and optional version match rule for the parent bundle that this fragment contributes to. You may use the Browse button to select a parent from a dialog of other bundles in the target platform. ||None|
|Minimum Version||The minimum version of the host plug-in||Host plug-in's minimum version|
|Maximum Version||The maximum version of the host plug-in||Host plug-in's minimum version|
|Search for dependencies automatically upon resource changes||Select this option to enable the tools to search for package dependencies whenever the user modifies referenced files. When this option is deselected, the tooling will not search for any unresolved or unused dependencies in your project.||Selected|
|Attempt to automatically resolve Manifest dependencies ||Select this option to enable the tools to automatically manage the package dependency information in the manifest file. Package dependencies in your project's Java code will automatically be reflected through proper updates to the manifest file. When this option is deselected, package dependencies that are not properly reflected in the manifest are flagged with problem markers, along with quick fixes to resolve the problems.||Selected|
|Give preference to Require-Bundle ||Require-Bundle will be used to automatically resolve a package dependency in cases where either Require-Bundle or Import-Package can be used. ||Not selected|
|Give preference to Import-Package||Import-Package will be used to automatically resolve a package dependency in cases where either Require-Bundle or Import-Package can be used.||Selected |
This is followed by the Target Definition page:
Table 3. Target Definition options
|Target||Select from the list the Target Definition this Client Services Project will target. You can change your selection later in the Client Services property page.||Default Target|
|Target Features||Check the Target Definition Features that your Client Services Project requires from this tree of Target features. You can change your selection later in the Client Services property page. Grey entries are required by the Target Definition and cannot be un-checked. The user may also select any user defined features from this tree. These features display on top of this tree with a label of "User Defined Features". If this entry is not found on the tree, then either, this option is disabled in the preference page or the toolkit did not find any features and plug-ins in the configured location. ||The "Core OSGi Interfaces" Target Feature is required by all Target Definitions.|
Parent topic: Wizards: XPD621