Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

DSDP/MTJ/Manual Obfuscation

< DSDP‎ | MTJ
Revision as of 03:46, 24 November 2006 by Unnamed Poltroon (Talk)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Back to main DSDP-MTJ Use Cases


Short description:

Priority:

Owner:

Status:

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

Community Review: review_date_here


Use-Case Specification:


1. Use Case Description

The developer obfuscates the application compiled code using an external Java code obfuscator.

The Obfuscation is included as a task in the build process. Obfuscation task is one of other build tasks such as compilation, code reduction, preverification, packaging, signing, deployment and running. User can manage build process as he needs by adding tasks to build process. Managing build process is done in project properties.

Obfuscation build task needs to its running several attributes. User has to set up the obfuscator location path (user can choose from several external obfuscators) and obfuscator additional parameters (like command line parameters). These parameters are for the better future using saved in the Obfuscation configuration. Each configuration has unique name and it contains user defined attributes about the Obfuscator.

User can manage a configuration of obfuscation via preferences/properties pages. Global setting is done via the obfuscation preferences in global eclipse preferences page. Here user can create, edit or remove configurations of the Obfuscator. Assigning concrete configuration to the MTJ project is set up in the project properties. Here user can enable obfuscation task and choose from saved configuration which obfuscator is used.


2. Basic Flow

B1: User selects the application.
B2: User chooses to generate the obfuscated code.
B3: System verifies that the code is compiled. If not, an error message is displayed with an option to compile.
B4: The system obfuscates the compiled code using the external obfuscator specified in the project properties.
B5: The system notifies that the obfuscation was successfully executed or an error message is displayed in case of failure.


3. Alternate Flows


4. Preconditions

4.1 A MTJ project is installed in Eclipse and is compilable.

4.2 User has installed at least one Obfuscator and saved at least one the Obfuscation configuration. See: Configure Obfuscator


5. Postconditions

5.1 The obfuscated code is generated in the project folder

A code with the user defined parameters has been generated.


6. Extension Points


7. Special Requirements


8. Additional Information



Comments:


Back to main DSDP-MTJ Use Cases

Back to the top