Skip to main content
Jump to: navigation, search

DSDP/MTJ/Create Device Specific Build

< DSDP‎ | MTJ

Back to main DSDP-MTJ Use Cases


Short description:

The distributor of the application requests a separate jad- and jar-files for each supported device. The creation of the separate files is simple work and this can by automated by the help of the system.

Priority:

Owner:

Status:

Proposed:|Accepted: date_here
Identified|Described|Outlined|Detailed

Community Review: review_date_here


Use Case Specification: Create separate build for each device


1. Brief Description

The distributor of the application requests a separate jad- and jar-files for each supported device. The creation of the separate files is simple work and this can by automated by the help of the system.

A Java developer creates separate jad- and jar-files for each device to be used in distribution. The developer chooses to create a release build and to use the optional feature of creating a separate jad- and jar-files for each device. The system does the compilation and creates all the variations. During packaging the system creates jad- and jar files with individual names for each device. The files are stored in folders containing each folder only one variation but many jar and jad files with individual names.


2. Flow of events

2.1 Basic Flow

B1: The user chooses to create a release build
B2: The system shows the option of creating a separate build for each device.
B3: The user chooses to use this option.
B4: The system compiles all the wanted software variations.
B5: The system packages the compilation results and creates individual build files for each device.
B6: The system names the files based on the compilation device groups.
B7: The system changes the url-links in the jad-files to conform to the new names of the jar-files.
B8: The system stores the files into folders containing each folder results from only one software variation.


2.2 Alternative flows

Alternative flow 1:


3. Special Requirements


4. Preconditions

4.1 The target devices have been defined
The user has defined the target devices of the build. The names of the target devices are used as the source for the file names of the individually named build files.

4.2 Preprocessing info is in use
The system has stored the device group information from the preprocessing. The system knows for which devices each build is meant for.


5. Post Conditions

5.1 Individually named builds are available for each device
The system has created builds based on the chosen software variations. The system has additionally created enough copies from these builds that an individually named build can be provided for each device. The file names consists of the given application name plus the name of the device e.g. Midlet_Nokia_5500.jar and Midelt_Nokia_5500.jad.

5.2 The url-links in the jad-files conform to the jar-names
The system has modified the url-links in the jad-files to conform to the names of the jar-files.

5.3 Builds are stored in folders containing one software variation
The system has stored the created builds into file folders containing builds basing on one software variation. The only differences between the builds in one folder are the names of the files and the url-link in the jad-file.


6. Extension Points



Comments:


Back to main DSDP-MTJ Use Cases

Back to the top