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

Bug 359058

Summary:	[Refactoring - Architecture] Identify the layers and sub-layers for the Papyrus architecture
Product:	[Modeling] Papyrus	Reporter:	Camille Letavernier <cletavernier>
Component:	Core	Assignee:	Project Inbox <mdt-papyrus-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:
Bug Depends on:
Bug Blocks:	359063

Description Camille Letavernier

2011-09-27 09:33:42 EDT

We should identify the different layers and sub-layers for the Papyrus architecture.

The higher-level layers should identify a domain (Core, EMF, UML, ...)

The sub-level layers should identify a technology (Diagrams, Tables, Properties, ...)

Comment 1 Camille Letavernier

2011-10-18 07:57:43 EDT

See trunk/doc/DevelopperDocuments/architecture/refactoring/org.eclipse.papyrus.dev.refactoring on the SVN

Comment 2 Camille Letavernier

2011-12-01 04:00:52 EST

Done

Comment 3 Camille Letavernier

2012-03-19 11:29:46 EDT

The following plug-ins, which were excluded from the initial refactoring, were moved to their right layer or folder, in r7449~7465:

oep.navigator: deprecated
outline.emftree: example
parsers: extra/marte
svn: team
readonly: infra/emf
extensionpoints.editor: infra/gmfdiag
resource: deprecated
resource.edit: deprecated
sysml.converted: deprecated
resource.migration: deprecated
uml.standard.converted: deprecated
constraintwithessentialocl.editor.xtext: deprecated (duplicate)
xtext.gmf.glue: infra/gmfdiag

The *.psf files still need to be updated : 
Bug 363440: [Refactoring - SVN] Papyrus should provide a set of *.psf files
The packages still need to be renamed.
Bug 362162: [Architecture - Refactoring] The plug-ins should be renamed to match their layer's qualified name