Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 330187

Summary:	[SysML Internal Block Diagram] Papyrus shall provide an editor for SysML Internal Block Diagrams (IBD).
Product:	[Modeling] Papyrus	Reporter:	Sébastien Gérard <sebastien.gerard>
Component:	Core	Assignee:	Project Inbox <mdt-papyrus-inbox>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3	Keywords:	plan
Version:	unspecified	Flags:	sebastien.gerard: indigo+
Target Milestone:	M6
Hardware:	PC
OS:	All
Whiteboard:	Editors

Description Sébastien Gérard

2010-11-13 17:42:49 EST

[Block Definition Diagram] Papyrus shall provide an editor for SysML Internal Block Diagrams (IBD).

Comment 1 Yann Tanguy

2011-08-19 09:32:31 EDT

In r5275 (0.8.1) & r5276 (trunk)
- Alignment with current BDD (label, graphical representation...)

Comment 2 Patrick Tessier

2012-01-17 08:07:29 EST

export packages in order to be able to pilot it programmatically
done in the head 6880 and in the branch 6882

Comment 3 Yann Tanguy

2012-01-19 05:58:37 EST

(In reply to comment #2)
> export packages in order to be able to pilot it programmatically
> done in the head 6880 and in the branch 6882

Exporting everything does not appear to be a good option and lead to maintenance issues. 

This should not have been added in SR2 and has to be reverted. Diagrams should only expose API that are planned to be maintained not the full code. If such API does not exist it should be defined and implemented. 

Another possible choice is to export the all the code, but using "internal" package to distinguish the code that is not expected to be freely used by other plug-ins. In such a case needed API still require to be defined and implemented.

An enhancement task request should be added describing your need.

Comment 4 Camille Letavernier

2013-03-25 08:19:01 EDT

Papyrus provides the IBD diagram. I close this task.