Community
Participate
Working Groups
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, ...)
See trunk/doc/DevelopperDocuments/architecture/refactoring/org.eclipse.papyrus.dev.refactoring on the SVN
Done
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