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.
Difference between revisions of "DSDP/MTJ/Remove Debug Features from Release Build"
| Line 18: | Line 18: | ||
Use Case Specification: Remove debug features from release build | Use Case Specification: Remove debug features from release build | ||
| − | 1. Brief Description | + | '''1. Brief Description''' |
The duty of the Java developer when creating a release build is to make sure that the build is ready for release. One of the acts to fulfill this is to remove the debug features from the build. | The duty of the Java developer when creating a release build is to make sure that the build is ready for release. One of the acts to fulfill this is to remove the debug features from the build. | ||
| Line 25: | Line 25: | ||
| − | 2. Flow of events | + | '''2. Flow of events''' |
| − | 2.1 Basic Flow<br/> | + | '''2.1 Basic Flow'''<br/> |
:B1: The user starts to make build | :B1: The user starts to make build | ||
:B2: The user chooses between | :B2: The user chooses between | ||
| Line 41: | Line 41: | ||
| − | 3. Special Requirements | + | '''3. Special Requirements''' |
| − | 4. Preconditions | + | '''4. Preconditions''' |
| − | 4.1 Debug classes marked as debug classes<br/> | + | '''4.1 Debug classes marked as debug classes'''<br/> |
A Java developer has marked all the debug classes as debug classes | A Java developer has marked all the debug classes as debug classes | ||
| − | 4.2 Alternative methods are defined<br/> | + | '''4.2 Alternative methods are defined'''<br/> |
A Java developer has defined alternative methods for the methods in debug classes needing to be replaced with something. | A Java developer has defined alternative methods for the methods in debug classes needing to be replaced with something. | ||
| − | 5. Post Conditions | + | '''5. Post Conditions''' |
| − | 5.1 Release build has been created without debug features<br/> | + | '''5.1 Release build has been created without debug features'''<br/> |
The user has created the release build for sure without debug features. The user can continue with the build into the next steps of the deployment process without a risk of accidentally releasing a debug build. | The user has created the release build for sure without debug features. The user can continue with the build into the next steps of the deployment process without a risk of accidentally releasing a debug build. | ||
| − | 6. Extension Points | + | '''6. Extension Points''' |
---- | ---- | ||
| − | Comments: | + | '''Comments:''' |
Back to main [[DSDP-MTJ Use Cases]] | Back to main [[DSDP-MTJ Use Cases]] | ||
Revision as of 07:17, 14 November 2006
Back to main DSDP-MTJ Use Cases
Short description:
Before releasing the SW build, debug information must be removed from the source code
Priority:
Owner:
Status: Proposed, Outlined
- Proposed:|Accepted: date_here
- Identified|Described|Outlined|Detailed
Community Review: review_date_here
Use Case Specification: Remove debug features from release build
1. Brief Description
The duty of the Java developer when creating a release build is to make sure that the build is ready for release. One of the acts to fulfill this is to remove the debug features from the build.
A Java developer chooses from the build operations that the build is a release build. The system removes all debug features during the preprocessing.
2. Flow of events
2.1 Basic Flow
- B1: The user starts to make build
- B2: The user chooses between
- (1) development build
- (2) release build
- B3: The user chooses to build a release build
- B4: The system starts the compiling and detects during the preprocessing all the debug classes.
- B5: The system removes the debug classes and their methods and replaces some methods.
- B6: The system creates the release build without the debug features
- Alternative flows
- Alternative flow 1: The user chooses a development build.
3. Special Requirements
4. Preconditions
4.1 Debug classes marked as debug classes
A Java developer has marked all the debug classes as debug classes
4.2 Alternative methods are defined
A Java developer has defined alternative methods for the methods in debug classes needing to be replaced with something.
5. Post Conditions
5.1 Release build has been created without debug features
The user has created the release build for sure without debug features. The user can continue with the build into the next steps of the deployment process without a risk of accidentally releasing a debug build.
6. Extension Points
Comments:
Back to main DSDP-MTJ Use Cases