Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 366026 - [ActivityDiagram] Refactoring in order to try respect Generation Gap Pattern
Summary: [ActivityDiagram] Refactoring in order to try respect Generation Gap Pattern
Status: RESOLVED FIXED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: 0.8.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-08 08:05 EST by Arthur Daussy CLA
Modified: 2015-03-17 05:57 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Arthur Daussy CLA 2011-12-08 08:05:35 EST 
This aim of this bug is to have a long term opened bug to commit all changes would concern trying to make this diagram more respectful of Generation Gap Pattern.

To be clear the aim of is bug is to collect all commit that would avoid to create generated not tag.

For example with re-routing EditPart factory to use Custom Edit Part.
Comment 1 Arthur Daussy CLA 2011-12-08 11:36:46 EST 
Commit has been made on the branch 0.8.x.

With this commit ControlFlowEditPart, ObjectFlowEditPart, ObjectFlowSelectionEditPart and ObjectFlowTransforamtionEditPart has been integrated into the new generation gap pattern mechanism.

That is to say those EditPart are now free from "generate not" tag. All custom code is now in the respective custom class.
Comment 2 Camille Letavernier CLA 2015-03-17 05:57:03 EDT 
Further improvements tracked in Bug 404119