Release Notes for Older Version of Sirius

1. Release Notes for Older Version of Sirius
   1. Changes in Sirius 1.0.0 (from Sirius 1.0.0M7)
      1. User-Visible Changes
      2. Specifier-Visible Changes
      3. API Changes
   2. Changes in Sirius 1.0.0M7 (from Sirius 1.0M6)
      1. Specifier-Visible Changes
      2. API Changes
   3. Changes in Sirius 1.0.0M6 (from Sirius 1.0M5)
      1. API Changes
   4. Changes in Sirius 1.0.0M5 (from Sirius 1.0M4)
      1. User-Visible Changes
      2. API Changes
   5. Changes in Sirius 1.0.0M4 (from Sirius 0.9)
      1. User-Visible Changes
      2. API Changes
   6. Changes in Sirius 0.9.0
      1. Migrating from Obeo Designer or Viewpoint to Sirius
      2. Plug-ins version numbers.
      3. Major namespace changes
      4. Nature ID
      5. Other API Changes
      6. Specifier-Visible Changes
      7. User-Visible Changes

This document contains the release notes for older versions of of Sirius.

Changes in Sirius 1.0.0 (from Sirius 1.0.0M7)

User-Visible Changes

• The ability to print table representations has been disabled for the 1.0.0 release due to an external dependency issue (see bug #435204 for the details).

Specifier-Visible Changes

• Node, Container and Edge mappings can not be created as direct children of a Diagram Description anymore, the first level mappings must be created as direct children of a Layer.
• Mapping (resp. tools) can not be added as reused mapping (resp. tools) of a Diagram Description, they must be added to the reused mappings (resp. tools) of a Layer. The corresponding property sections will be shown only for old VSM with reused elements.

API Changes

Changes in org.eclipse.sirius

• In package org.eclipse.sirius.business.api.control, the constructors of SiriusControlCommand and SiriusUncontrolCommand which assume implicitly that the session should be saved as part of the command are now deprecated. Use the alternative constructors (a new one has been added to SiriusUncontrolCommand) to say explicitly if the command should save the session. Most code should do the save themselves outside of the command, and thus pass false to the shouldEndBySaving argument of these constructors.
• In package org.eclipse.sirius.business.api.session, class SavingPolicyImpl (the default session saving policy) now inherits from the new AbstractSavingPolicy class. The new abstract class can be used as a base to implement different policies by simply overriding the computeResourcesToSave() method.

Changes in org.eclipse.sirius.diagram.ui

• To enable the resize of border nodes whose parent is a list, the createLayoutEditPolicy and getResizeBorderItemCommand methods have been extracted from org.eclipse.sirius.diagram.ui.edit.api.part.AbstractDiagramContainerPart and placed into org.eclipse.sirius.diagram.ui.edit.api.part.AbstractDiagramElementContainerEditPart. The org.eclipse.sirius.diagram.ui.edit.api.part.AbstractDiagramListEditPart.createLayoutEditPolicy implementation has been removed.

Changes in org.eclipse.sirius.diagram.ui

• org.eclipse.sirius.editor.tools.api.menu.AbstractMenuBuilder.getLabel() visibility has been changed from protected to public.
• org.eclipse.sirius.editor.tools.api.menu.CompositeMenuBuilder has been introduced to avoid duplicated menu. A CompositeMenuBuilder is created to encapsulate AbstractMenuBuilder with the same label.

Changes in Sirius 1.0.0M7 (from Sirius 1.0M6)

Specifier-Visible Changes

• The default value of the Semantic Candidates Expression for Tree Items has changed from an empty string (meaning “any compatible element in the session”) to feature:eAllContents which only looks for compatible candidates inside the current element (recursively). The new behavior is more efficient on large models and consistent with what happens for diagrams. The change does not affect existing VSMs which continue to work as before whatever was the expression they used. Users who want the old behavior on specific mappings can simply remove the expression in the properties view.
• In the Time Profiler view, the Time (hh:mm:ss,ms) has been removed. It was redundant with the existing Time (ms) column, harder to read/sort, and showed wrongly formatted results.

API Changes

Move diagram.ecore in its own plugin

This milestone (Sirius 1.0M7) includes the third, and final, step towards a full separation of the diagram-specific stuff out of the core of Sirius (see Step1 and Step2 for more details).

All classes related to diagrams in org.eclipse.sirius have been moved to org.eclipse.sirius.diagram.
All classes related to diagrams in org.eclipse.sirius.ui have been moved to org.eclipse.sirius.diagram.ui.
All classes related to diagrams in org.eclipse.sirius.editor have been moved to org.eclipse.sirius.editor.diagram.
In the same way, all classes related to UI in org.eclipse.diagram have been moved to org.eclipse.sirius.diagram.ui. To simplify this step almost all classes of org.eclipse.diagram have been moved in org.eclipse.sirius.diagram.ui (and probably not only UI classes). These classes have been moved in src-diag source folder to facilitate future work about moving some of these classes in org.eclipse.diagram again.

Unlike, the Step1, a simple “Organize Imports” operation is not enough. First, you will probably need to add dependencies to org.eclipse.sirius.diagram, org.eclipse.sirius.diagram.ui or org.eclipse.sirius.editor.diagram in the MANIFEST.MF of your projects that depend on Sirius diagram classes. The dependencies to add depend on what you really use.

• ViewpointRegistry.getDiagramDescriptionMappingsRegistry() has been removed. You can now directly call org.eclipse.sirius.diagram.business.api.componentization.DiagramDescriptionMappingsRegistry.INSTANCE.DialectServices.
• New methods have been added to IRepairParticipant to isolate specific diagram repair steps.
  • removeElements(DView, TransactionalEditingDomain, IProgressMonitor): Removes elements from the DView that will be recreated by the refresh (called later).
  • cleanRepresentations(EList<DRepresentation>): Cleans representations (specific representation states like filters) and eventually returns some of them if they need to be removed.
  • refreshRepresentations(DAnalysis, DView): This method is only implemented by the diagram participant. To simplify work for this step, this method manages core and diagram elements. It should be clean up once the split will be done.
• To break the dependencies from Core to Diagram, several services have been added to:
  • DialectServices, with default implementations in AbstractRepresentationDialectServices:
    • createTask(CommandContext, ModelAccessor, ModelOperation, Session, UICallBack): Creates a new task corresponding to the ModelOperation. Only needed for ModelOperation specific to one dialect.
    • handles(RepresentationExtensionDescription): Tells if the current dialect handles the given RepresentationExtensionDescription.
    • invalidateMappingCache(): Allows each dialect to clean and compute again its proper mapping cache.
    • allowsEStructuralFeatureCustomization(EObject): allows dialects to indicate if they allow EStrucuralFeaturesCustomization for the given VSM element. It is currently supported for style descriptions in diagrams only.
  • DialectUIServices
    • canHandle(RepresentationDescription) and canHandle(RepresentationExtensionDescription): tell whether the dialect is able to handle the given representation description or extension description.
    • completeToolTipText(String, EObject) allows the dialect to customize the tooltip displayed in a property section of a given VSM element.
  • DialectUIManager
    • canExport(DRepresentation, ExportFormat): New method returning true if at least one dialect is able to export this representation to this format, false otherwise.
  • IDiagramDescriptionProvider
    • completeToolTipText(String, EObject) allows the diagram type to customize the tooltip displayed in a property section of a given VSM element. SequenceDiagramTypeProvider implements this method to mention some Sequence specific variable available in core and diagram tool preconditions in the context of a Sequence diagram.
• All methods of SiriusHelper concerning diagrams have been moved to org.eclipse.sirius.diagram.business.api.helper.SiriusDiagramHelper.
• All methods of SiriusUtil concerning diagrams have been moved to org.eclipse.sirius.diagram.business.api.helper.SiriusDiagramUtil.
• All methods of org.eclipse.sirius.business.api.query.EObjectQuery concerning diagrams have been moved to org.eclipse.sirius.diagram.business.api.query.EObjectQuery.
• Library Extensions:
  • All methods depending only on draw2d of org.eclipse.sirius.diagram.ui.tools.api.draw2d.ui.figures.FigureUtilities have been moved in org.eclipse.sirius.ext.draw2d.figure.FigureUtilities
  • fr.obeo.dsl.viewpoint.diagram.ui.tools.api.layout.GraphicalHelper has been moved to org.eclipse.sirius.ext.gmf.runtime.editparts.GraphicalHelper.
  • org.eclipse.sirius.diagram.part.SiriusDiagramEditorPlugin has been renamed into org.eclipse.sirius.diagram.DiagramPlugin. This plugin is not a UI plugin any more, org.eclipse.sirius.diagram.ui.provider.DiagramUIPlugin.getPlugin() should be used instead for UI related aspects. For example DiagramUIPlugin.getPlugin().getPreferenceStore() should be used instead of DiagramPlugin.getDefault().getPreferenceStore() or SiriusDiagramEditorPlugin.getInstance().getPreferenceStore().
• DeleteFromDiagramContributionItem and SetStyleToWorkspaceImageContributionItem have been merged into SiriusActionBarActionContributionItem
• Images
  • Images of org.eclipse.sirius.diagram have been moved to org.eclipse.sirius.diagram.ui. In your code, you should replace SiriusDiagramEditorPlugin.getInstance().getImage() and DiagramPlugin.getInstance().getImage() by DiagramUIPlugin.getPlugin().getImage(). That is the case for all methods concerning images in DiagramPlugin (previously named SiriusDiagramEditorPlugin).
  • Some images of org.eclipse.sirius.ui have been moved to org.eclipse.sirius.diagram.ui, the corresponding constants in org.eclipse.sirius.ui.tools.api.image.ImagesPath have been moved in org.eclipse.sirius.diagram.ui.tools.api.image.DiagramImagesPath.
• The method static void refreshSelection(DiagramElementMapping) from org.eclipse.sirius.editor.tools.api.menu.AbstractEObjectRefactoringAction is not available anymore.
• Preferences
  • org.eclipse.sirius.business.api.preferences.SiriusPreferencesKeys.PREF_AUTO_PIN_ON_CREATE has been moved to org.eclipse.sirius.diagram.tools.api.preferences.SiriusDiagramPreferencesKeys.
• Ids
  • The Sirius diagram editor id is now org.eclipse.sirius.diagram.ui.part.SiriusDiagramEditorID
  • Its property contributor is now org.eclipse.sirius.diagram.ui. This id has to be changed in plugins providing additional property sections to the Sirius diagram editor (created with EEF for example).

Moved extension points

Several extension points have been moved:

• from org.eclipse.sirius to org.eclipse.sirius.diagram. You should change the id of the following extension point in your plugin.xml ( org.eclipse.sirius.xxxx replaced by org.eclipse.sirius.diagram.xxxx):
  • diagramTypeProvider
• from org.eclipse.sirius.diagram to org.eclipse.sirius.diagram.ui. You should change the id of the following extension points in your plugin.xml ( org.eclipse.sirius.diagram.xxxx replaced by org.eclipse.sirius.diagram.ui.xxxx):
  • diagramIdentifierProvider
  • imageSelector
  • layoutDataManager
  • layoutProvider
  • styleConfigurationProvider
  • viewOrderingProvider

Changes in org.eclipse.sirius.common

• In class org.eclipse.sirius.common.tools.api.util.EclipseUtil, the method getExtensionPlugins(Class<T>, String, String, String, Predicate<String>) has been removed from API to avoid exposing a Guava-specific Predicate. Instead, use the new method getExtensionPluginsByKey() which returns all the extensions organized by the specified key, and filter the result according to whatever critera the Predicate tested on the key.

Changes in org.eclipse.sirius

• org.eclipse.sirius.business.api.query.URIQuery.isSiriusEnvironmentURI has been replaced by
  • isSiriusCoreEnvironmentURI which checks that the given resource is the Sirius core Environment.xmi file.
  • and isEnvironmentURI which checks that the given resource has an environment uri scheme.
• In org.eclipse.sirius.business.api.dialect.DialectManager
  • the setter setRefreshActivatedOnRepresentationOpening(boolean) has been removed as the refresh on opening should be managed from the corresponding preference org.eclipse.sirius.ui.business.api.preferences.SiriusUIPreferencesKeys.PREF_REFRESH_ON_REPRESENTATION_OPENING.
  • isRefreshActivatedOnRepresentationOpening() has been moved into org.eclipse.sirius.ui.business.api.dialect.DialectUIManager as it refers to an UI behavior.
• The DRepresentation.createContents() (both variants) and DRepresentation.updateContents() EOperations have been removed. They were not used anywhere.
• The org.eclipse.sirius.business.api.modelingproject.ModelingProject.MODELING_PROJECT_PREDICATE constant has been removed to reduce Sirius’s exposure of Guava’specific types. Use the equivalent ModelingProject.hasModelingProjectNature() method instead.
• The method org.eclipse.sirius.business.api.query.EObjectQuery.getInverseReferences(Predicate<Setting>) has been removed from API to avoid exposing a the Guava-specific Predicate type.
• In class org.eclipse.sirius.business.api.dialect.description.AbstractInterpretedExpressionQuery, the protected methods appendAllLocalVariableDefinitions() and appendEditMaskVariables() now take a Map<String, Collection<String>> instead of a Guava-specific Multimap. The new protected method addDefinition() can be used to make it easier to add entries to the map. Subclasses in Sirius have been updated to match the new signature.
• The message org.eclipse.sirius.business.api.modelingproject.ModelingProject.ZERO_REPRESENTATIONS_FILE_FOUND_IN has been removed without replacement. It was not really an API constant.
• The behavior of method org.eclipse.sirius.business.api.modelingproject.ModelingProject.getMainRepresentationsFileURI() has changed. It now marks this project as invalid and adds a marker on it, if it is considered as invalid (no or many representations files).
• A new query org.eclipse.sirius.business.api.query.IFileQuery has been added with a method to check if file is handled by an opened session, ie:
  • a semantic resource of this session,
  • a referenced sub representations file,
  • a controlled resource.
• The EObjectLink class has been removed from the metamodel. It was not used anywhere.
• In interface org.eclipse.sirius.business.api.dialect.description.IInterpretedExpressionTargetSwitch, the getFirstRelevantContainerFinder() method which returned a Guava Function<EObject, EObject> has been replaced with the new method getFirstRelevantContainer(EObject) which directly returns the result of applying the previously returned function. All implementers in Sirius itself have been updated.
• The constructor org.eclipse.sirius.business.api.dialect.description.DefaultInterpretedExpressionTargetSwitch(EStructuralFeature, IInterpretedExpressionTargetSwitch, Function<EObject, EObject>) has been removed to avoid exposing a the Guava-specific Predicate type. Sub-classes which used it with a non-null Function should override the getFirstRelevantContainer(EObject) method to return the result of that function instead.
• The org.eclipse.sirius.business.api.helper.task.AbstractDeleteDRepresentationElementTask constructor which took a Guava Predicate<EReference> now takes an equivalent EReferencePredicate (from org.eclipse.sirius.ext.emf).
• The constants DSEMANTICDECORATOR_REFERENCE_TO_IGNORE_PREDICATE and NOTATION_VIEW_ELEMENT_REFERENCE_TO_IGNORE_PREDICATE from org.eclipse.sirius.business.internal.session.danalysis.DanglingRefRemovalTrigger are now instances of EReferencePredicate instead of Guava’s Predicate<EReference>.
• In class org.eclipse.sirius.business.api.session.SessionEventBroker, the method addlLocalTrigger() now takes a org.eclipse.emf.transaction.NotificationFilter instead of a Guava-specific Predicate<Notification> as first argument.
• The constant org.eclipse.sirius.tools.api.ui.RefreshEditorsPrecommitListener.IS_IMPACTING is now a NotificationFilter instead of a Predicate, to match the API change in SessionEventBroker.addLocalTrigger().
• The org.eclipse.sirius.business.api.session.Session interface has a new getSavingPolicy() method which gives access to the currently configured saving policy.

Changes in org.eclipse.sirius.diagram

• The references DNode.ownedDetails and DDiagramElementContainerImpl.ownedDetails have been removed from the metamodel, along with the corresponding implementation methods. They were not used in practice.
• The DDiagramLink EClass has been removed from the meta-model, along with the corresponding generated Java code. It was not used in practice.
• The DDiagram.clean() EOperation has been removed. It was deprecated and not used anymore. All the Java code which existed only to help in the implementation of that operation has also been removed. This includes:
  • The org.eclipse.sirius.diagram.tools.api.validation.constraint.AbstractDDiagramConstraint.activate() and deactivate() methods.
  • The org.eclipse.sirius.business.api.helper.SiriusHelper.unSetHarmlessDanglingReferences() method.
  • The org.eclipse.sirius.tools.api.profiler.SiriusTasksKey.CLEANING_NODES_KEY constant.
• The DSemanticDiagram.getRootContents() method (which was deprecated) has been removed.
• The DDiagram.findDiagramElements() EOperation has been removed. It was deprecated and always returned an empty list if called.
• The DDiagram.info attribute has been removed. It was not used anywhere.
• The DDiagram.subDiagram reference has been removed. It was not used anywhere.
• The DDiagramElement.isFold() EOperation has been removed. It was deprecated and edge folding has long been implemented using different mechanisms.
• In the ContainerMapping type, the following EOperations have been removed: createContainer(), updateContainer(), and getNodesCandidate(). Although their usage is highly discouraged, if you really need to you can currently use the corresponding methods in the internal ContainerMappingHelper instead (use SiriusPlugin.getDefault().getInterpreterRegistry().getInterpreter(semanticElement) to obtain the IInterpreter those methods need). As with all internal code, there is no guarantee these methods will still exist in future versions.
• The AbstractNodeMapping.getDNodesDone() EOperation has been removed. It was not used anywhere.
• In the NodeMapping type, the getBestStyle() and createListElement() EOperations have been removed. Although their usage is highly discouraged, if you really need to you can currently use the corresponding methods in the internal MappingHelper instead (use SiriusPlugin.getDefault().getInterpreterRegistry().getInterpreter(semanticElement) to obtain the IInterpreter these methods need). As with all internal code, there is no guarantee these methods will still exist in future versions.
• In interface org.eclipse.sirius.diagram.business.api.diagramtype.IDiagramDescriptionProvider, the methods allowsPinUnpin(), allowsHideReveal, and allowsCopyPasteLayout() have been modified to take directly the DDiagramElement to test (and return a boolean) instead of returning a Guava-specific Predicate which then had to be invoked.
• In class org.eclipse.sirius.diagram.ui.tools.api.layout.PinHelper, .the method allowsPinUnpin() has been modified to take a DDiagramElement directly and return a boolean, instead of taking a DDiagram and return a Guava-specific Predicate which then had to be invoked on actual DDiagramElements..
• The interface org.eclipse.sirius.diagram.ui.edit.api.part.ISiriusEditPart has been added and is now part of all the type hierarchy of any EditPart provided by Sirius. This allows a simple instanceof ISiriusEditPart to discriminate the edit part instances coming from Sirius.

Changes in org.eclipse.sirius.diagram.sequence

• The org.eclipse.sirius.diagram.sequence.util.SiriusFunctions class has been removed. It was not used anywhere.
• The org.eclipse.sirius.diagram.sequence.util.NotificationQuery class has been removed. It had been exposed by mistake.
• The org.eclipse.sirius.diagram.sequence.business.internal.util.NotationPredicate class has been removed from API, to reduce Sirius’s exposure of Guava’specific types.
• All the static methods in org.eclipse.sirius.diagram.sequence.util.Range which returned Guava-specific types ( Function or Ordering) have been removed from API.
• org.eclipse.sirius.diagram.sequence.template.AbstractRule no longer inherits from Guava’s Function interface, but from the news ad-hoc org.eclipse.sirius.diagram.sequence.template.Transformer interface instead, which is functionally equivalent.

Changes in org.eclipse.sirius.ui

• org.eclipse.sirius.ui.business.api.preferences.DesignerUIPreferencesKeys has been renamed into org.eclipse.sirius.ui.business.api.preferences.SiriusUIPreferencesKeys
• Methods getMissingDependencies() and getMissingDependenciesErrorMessage() from org.eclipse.sirius.ui.business.api.viewpoint.ViewpointSelection now use Map<String, Collection<String>> instead of Guava’s Multimap.
• org.eclipse.sirius.ui.tools.api.project.ModelingProjectManager.initializeAfterLoad() method has been removed. There is no replacement for this method documented as “Not intended to be used by client”.

Changes in org.eclipse.sirius.ecore.extender

• All variants of eDelete() methods which took a Predicate<EReference> in types ModelAccessore, IMetamodelExtender and CompositeMetamodelExtender now take an equivalent EReferencePredicate (from org.eclipse.sirius.ext.emf).
• The ModelUtils.resolveAll(ResourceSet set, EReferencePredicate) now takes an EReferencePredicate instead of a Guava-specific Predicate<EReference>.

Changes in org.eclipse.sirius.ext.base

• The org.eclipse.sirius.ext.base.Options.isSome() method has been removed to reduce Sirius’s exposure of Guava’specific types. Use Option.some() directly instead.
• org.eclipse.sirius.ext.base.relations.Relation no longer inherits from com.google.common.base.Function, but keeps the same API otherwise.

Changes in org.eclipse.sirius.synchronizer

• The org.eclipse.sirius.synchronizer.Mapping.IS_CHECK_ONLY constant has been removed to reduce Sirius’s exposure of Guava’specific types. Use !Mapping.getCreator().some() instead.
• The Maybe and MaybeFactory types have been removed, and all their uses in org.eclipse.sirius.synchronizer converted to the equivalent Option and Options types from org.eclipse.sirius.ext.base.
• The internal class MappingHiearchy.HiearchyIterator has been removed from API.

Changes in org.eclipse.sirius.tests.support

• The shouldReloadSession boolean parameter has been removed from org.eclipse.sirius.tests.support.api.SiriusTestCase.disableUICallBackOnDialectEditor(DialectEditor), it was not used and could let the tester think he can change the reload behavior from the dialog factory.
• org.eclipse.sirius.tests.swtbot.support.api.AbstractSiriusSwtBotGefTestCase.refreshDiagram() has been removed. This method did not handle the non dynamic tabbar and was a duplicate of manualRefresh(). Callers must select the diagram before the call,the click(0,0) instruction was not sufficient in several cases (for example if there is a node/container in (0,0)).
• org.eclipse.sirius.tests.swtbot.support.api.editor.SWTBotDesignerEditor has been renamed into SWTBotSiriusDiagramEditor.
• org.eclipse.sirius.tests.swtbot.support.api.editor.SWTBotDesignerGefViewer has been renamed into SWTBotSiriusGefViewer.
• org.eclipse.sirius.tests.swtbot.support.api.editor.SWTBotDesignerHelper has been renamed into SWTBotSiriusHelper.
• Methods AbstractSiriusSwtBotGefTestCase.openRepresentation with SWTBotDesignerEditor as returned type have been renamed into openDiagram, marked as deprecated and replaced with methods returning a SWTBotEditor. You can now use methods openRepresentation for DTree or DTable. If the expectedRepresentationClass is DDiagram.class, the returned type will be a SWTBotSiriusDiagramEditor.
• Method org.eclipse.sirius.tests.swtbot.support.api.editor.SWTBotSiriusHelper.getDesignerEditor(String) has been renamed into getSiriusDiagramEditor.
• Add SWTBotSiriusHelper.getSiriusEditor(String) to return the SWTBotEditor (diagram, tree or table editor) with the given name. The name is the name as displayed on the editor’s tab in Eclipse. In case of multiple editors with the same fileName, the same method with an additional parameter, the index, has been added SWTBotSiriusHelper.getSiriusEditor(String, int).
• Change the behavior of org.eclipse.sirius.tests.swtbot.support.api.editor.SWTBotSiriusDiagramEditor.zoom(ZoomLevel) to directly change the zoom level of the current diagram editor without trying to change it from the zoom combo in the tabbar.
• Add org.eclipse.sirius.tests.swtbot.support.api.editor.SWTBotSiriusDiagramEditor.zoomFromToolbar(ZoomLevel) to add possibility to explicitly change the zoom level from the tabbar.

Changes in Sirius 1.0.0M6 (from Sirius 1.0M5)

API Changes

High-level API for Automated Tests Using JUnit and SWTBot

Starting from version 1.0.0M6, Sirius includes high-level APIs to help creating automated tests using JUnit and/or SWTBot. These can be used either to test Sirius itself or to test Sirius-based modelers. These APIs are provided by two plug-ins:

• org.eclipse.sirius.tests.support: support code for JUnit (plug-in) tests using Sirius.
• org.eclipse.sirius.tests.swtbot.support: support code for SWTBot tests using Sirius.

Both plug-ins are only available if you install the new org.eclipse.sirius.tests feature.

Move diagram-specific EPackages into their own diagram.ecore model

This milestone (Sirius 1.0M6) includes the second step towards a full separation of the diagram-specific stuff out of the core of Sirius (see Step1 for more details).

This step is less impactful on your code than the first step. Nevertheless, some missed classes during first step have moved during this step:

• Remove DDiagramSet and its corresponding reference from DRepresentationContainer: No longer needed
• DragAndDropTarget, DragAndDropTargetDescription and ContainerDropDescription have been moved to diagram EPackage.
• viewpoint/diagram/description/validation EPackage has been moved to viewpoint/description/validation: revert what was done in step 1 by mistake.

The existing VSM ( *.odesign) and representations file ( *.aird) are automatically migrated.

Warning: If you have some code based on the root EPackage of an EClass, it may be necessary to adapt it. Example:

EPackage rootPackage = (EPackage) EcoreUtil.getRootContainer(element.eClass());
if (rootPackage != null && rootPackage.getNsURI().equals(ViewpointPackage.eINSTANCE.getNsURI())) {

should be adapted in

EPackage rootPackage = (EPackage) EcoreUtil.getRootContainer(element.eClass());
if (rootPackage != null && rootPackage.getNsURI().equals(DiagramPackage.eINSTANCE.getNsURI())) {

if element is a Diagram concept.

Changes in org.eclipse.sirius

• The org.eclipse.sirius.tools.api.command.IDiagramCommandFactory.setAutoRefreshDView() method was removed. It had no effect, any code which called it can simply be removed.
• The deprecated interface org.eclipse.sirius.business.api.componentization.ViewpointRegistryListener has been removed. Use org.eclipse.sirius.business.api.componentization.ViewpointRegistryListener2 instead.
• org.eclipse.sirius.business.api.session.SessionManagerListener2 and org.eclipse.sirius.business.api.session.SessionManagerListener have been merged into org.eclipse.sirius.business.api.session.SessionManagerListener which is not deprecated any more.
• The deprecated method org.eclipse.sirius.business.api.session.SessionManagerListener.notifyUpdatedSession(Session) has been removed. Use org.eclipse.sirius.business.api.session.SessionManagerListener.notify(Session, int) instead.
• org.eclipse.sirius.business.api.helper.task.RemoveDanglingReferencesTask and org.eclipse.sirius.business.api.helper.task.RemoveSemanticDanglingReferenceTask and org.eclipse.sirius.tools.api.command.AbstractCommandFactory.addRemoveDanglingReferencesTask() have been removed. These tasks were added to in several commands to remove dangling references at the end. They are now replaced by a specific ModelChangeTrigger to detect the detachment of EObject and remove the dangling references. It is added to the SessionEventBroker during the session opening.
• org.eclipse.sirius.tools.api.ui.RefreshEditorsPrecommitListener was a precommit ResourceSetListener, it became a ModelChangeTrigger and is now added to the SessionEventBroker during the session opening. This modification allows to correctly manage the order of our different precommit commands. It is triggered after the dangling reference remover.
• org.eclipse.sirius.tools.api.command.semantic.RemoveDanglingReferences is no more used in Sirius commands. It can still be used to clean a resourceSet or a resource (repair tool, import/export, ..). It also has a new static method removeDanglingReferences(Resource) to remove dangling references as an entry point.
• The protected predicate org.eclipse.sirius.business.api.helper.task.AbstractDeleteDRepresentationElementTask.DSEMANTICDECORATOR_REFERENCE_T0_IGNORE_PREDICATE has been removed, the internal predicate DanglingRefRemovalTrigger.DSEMANTICDECORATOR_REFERENCE_T0_IGNORE_PREDICATE is used instead.
• The org.eclipse.sirius.business.api.helper.SiriusUtil.findDiagram(EObject) method has been removed. Use the equivalent new org.eclipse.sirius.business.api.query.EObjectQuery(element).getParentDiagram() instead.

Changes in org.eclipse.sirius.ui

• The org.eclipse.sirius.ui.tools.api.perspectives.DesignPerspective interface has been moved to org.eclipse.sirius.editor.tools.api.perspectives package in org.eclipse.sirius.editor plugin. This perspective is now provided through the org.eclipse.sirius.editor plugin. The perspective ID is kept unchanged for a compatibility reason.
• The deprecated class org.eclipse.sirius.ui.tools.api.dialogs.ExportRepresentationsAsImagesDialog has been removed. Use org.eclipse.sirius.ui.tools.api.dialogs.ExportSeveralRepresentationsAsImagesDialog instead.

Changes in org.eclipse.sirius.diagram

• org.sirius.diagram.graphical.edit.policies.AirNoteAttachmentEditPolicy has been removed, with the new dangling reference management, it became identical to its superclass, use org.eclipse.gmf.runtime.diagram.ui.internal.editpolicies.ConnectionEditPolicy instead. Its provider org.sirius.diagram.graphicalou .edit.policies.AirNoteAttachmentEditPolicyProvider and declaration in plugin.xml have been removed too.

Changes in org.eclipse.sirius.table

• The org.eclipse.sirius.table.tools.api.command.ITableCommandFactory.setAutoRefreshDTable() method was removed. It had no effect, any code which called it can simply be removed.

Changes in org.eclipse.sirius.tree

• The org.eclipse.sirius.tree.business.api.command.ITreeCommandFactory.setAutoRefreshDTree() method was removed. It had no effect, any code which called it can simply be removed.

Changes in Sirius 1.0.0M5 (from Sirius 1.0M4)

User-Visible Changes

• The table csv export has been improved to handle cropped label. In some specific cases, the cell label is automatically cropped and ‘...’ is concatenated to the resulting value. This cropped displayed label was previously exported, now the complete semantic value is exported.

API Changes

Library Extensions

This milestone (Sirius 1.0M5) introduces several new plug-ins, collectively called “library extensions”. They are all named org.eclipse.sirius.ext.LIB, where LIB is the name of a library or component Sirius depends on. These plug-ins are used to isolate generic code which extends existing libraries with features and helpers needed for Sirius, but which do not depend on Sirius themselves. A relatively large part of the code in Sirius is of this kind: things that could/should be in EMF, GMF, Eclipse itself, etc. and which are not Sirius-specific but which make it easier to build Sirius itself. Sirius 1.0M5 introduces several of these library extensions and starts to fill them with existing classes which were “hidden” inside Sirius and are now exposed in library extensions. Most of the time, existing code which used the Sirius API will only need to:

1. Add the necessary Import-Package (recommended) or Require-Bundle to depend on the library extension(s) where the code they use now lives;
2. Perform a simple “Organize Imports” operation, which should find the classes and interfaces in their new locations.

Move diagram-specific EClasses into a separate EPackage

For historical reasons, the core Sirius metamodels defined in viewpoint.ecore contain both generic (dialect-independant like Viewpoint, RepresentationDescription, DAnalysis...) concepts and diagram-specific ones (e.g. DNode, EdgeStyle, ContainerCreationDescription...). The table and tree metamodels are more cleanly separated.
This milestone (Sirius 1.0M5) includes the first step towards a full separation of the diagram-specific stuff out of the core of Sirius. So many EClasses have been moved.

Most of the time, existing code which used these Sirius EClasses will only need to perform a simple “Organize Imports” operation, which should find the classes and interfaces in their new locations.
The “Organize imports” is not sufficient in case of imported classes existing several time in different packages ( EFactory classes for example with DescriptionFactory, or EPackage classes for example with DescriptionPackage). And in some cases ViewpointFactory (and ViewpointPackage) will have to be replaced by DiagramFactory (and DiagramPackage).

The Switch classes if overridden also require a particular attention.

The existing VSM ( *.odesign) and representations file ( *.aird) are automatically migrated.
Warning: Nevertheless, if you reference these Sirius concepts with the EPackage qualifier in your VSM ( *.odesign), in interpreted expressions for example, you must change viewpoint in diagram. For example viewpoint::DDiagramElement becomes diagram::DDiagramElement.

The impacted EPackages are :

• viewpoint : some of its EClasses have been moved to viewpoint/diagram
• viewpoint/description : some of its EClasses have been moved to viewpoint/diagram/description
• viewpoint/description/style : some of its EClasses have been moved to viewpoint/diagram/description/style
• viewpoint/description/tool : some of its EClasses have been moved to viewpoint/diagram/description/tool
• viewpoint/description/filter : this EPackage has been moved to viewpoint/diagram/description/filter
• viewpoint/description/validation : this EPackage has been moved to viewpoint/diagram/description/validation
• viewpoint/description/concern : this EPackage has been moved to viewpoint/diagram/description/concern

Changes in org.eclipse.sirius

• The org.eclipse.sirius.business.api.migration.resource.StringCouple class has been removed.
• The org.eclipse.sirius.business.api.dialect.description.IInterpretedExpressionTargetSwitch.getFirstRelevantContainerFinder method has been added to let each dialect use its own Function to retrieve the first relevant container of a given EObject, i.e. the first container from which a domain class can be determined.

Changes in org.eclipse.sirius.common.ui

• The org.eclipse.sirius.common.ui.business.api.interpreter.VariableContentProvider class has been removed.
• The org.eclipse.sirius.common.ui.tools.api.util.ISimpleAction interface has been removed.
• The method org.eclipse.sirius.common.ui.tools.api.dialog.RenameDialog.setText() has been removed. You can now directly call org.eclipse.sirius.common.ui.tools.api.dialog.RenameDialog.setDefaultNewName() which has been added to set the default new name to display. Note that this method must be called before Dialog.create().
• The overriden method org.eclipse.sirius.common.ui.tools.api.dialog.RenameDialog.setTitle() has been removed. Note that the inherited setTile() method is still available but must be called before Dialog.create().

Changes in org.eclipse.sirius.table

• The org.eclipse.sirius.table.business.api.query.DCellQuery.getExportableLabel() method has been added to compute the label to export when the label is cropped by the org.eclipse.emf.edit.provider.ItemPropertyDescriptor.ItemDelegator.

Changes in org.eclipse.sirius.table.ui

• The org.eclipse.sirius.table.ui.business.api.helper.TableUIHelper now uses DCellQuery.getExportableLabel() to compute the cell labels used in HTML export.

Changes in org.eclipse.sirius.ui

• The long-deprecated org.eclipse.sirius.ui.business.api.session.DeprecatedIEditingSession interface has been removed. Use the corresponding methods from org.eclipse.sirius.ui.business.api.session.IEditingSession instead.

Changes in Sirius 1.0.0M4 (from Sirius 0.9)

User-Visible Changes

• The ability to print table representations, which had been disabled for the 0.9 release, has been re-enabled.

API Changes

Sirius 1.0.0M4 includes a lots of API-breaking changes, as part of a global effort to improve the quality of the Sirius internals. In this milestone in particular, most of the APIs which were marked as deprecated in previous versions of Sirius (and before that of Viewpoint) have been either removed (if a replacement exists) or marked as non-deprecated (if no replacement exists yet).

Changes in org.eclipse.sirius.common

• Two deprecated constructors have been removed in FeatureEditorDialog. Use the remaining constructor instead, which provides proper behavior for both unique and non-unique features.
• The deprecated method IEditingDomainFactory.createEditingDomain() has been removed. Use the (inherited) createEditingDomain(ResourceSet) instead, which ensures correct behavior for all kinds of models (Xtext for example).
• The deprecated field org.eclipse.sirius.common.tools.api.listener.Notification.FOLD has been removed. It was never used by Sirius itself, so if your code tried to listen to this kind of notification it was never actually called and can be safely removed.
• The deprecated methods getExtensionPlugins() and getElementsProvidedByPlugin from EcliseUtil have been removed. If you need this kind of functionality, use the Eclipse APIs directly instead.
• The deprecated fields COLUMN_SEMANTIC and LINE_SEMANTIC of IInterpreterSiriusVariables have been removed. Use the constants of org.eclipse.sirius.table.tools.api.interpreter.IInterpreterSiriusTableVariables instead.

Changes in org.eclipse.sirius

• The deprecated method DialectServices.initRepresentations(Viewpoint, EObject) has been removed. Use the version which takes an additional IProgressMonitor instead.
• The deprecated constructor in CreateRepresentationCommand has been removed. Use the alternative constructor which takes an additional IProgressMonitor instead.
• The two deprecated constructors in RefreshRepresentationCommand have been removed. Use the alternative constructors which take an additional IProgressMonitor instead.
• The deprecated method DisplayService.computeVisibility(Session, DDiagram, DDiagramElement) has been removed. Use the variant computeVisibility() which takes a DiagramMappingsManager instead of a Session.
• The following deprecated methods in FilterService have been removed:
  • activateCache(): use DisplayService.activateCache() instead.
  • deactivateCache(): use DisplayService.deactivateCache() instead.
  • activate(): use DisplayService.activate() instead.
  • deactivate(): use DisplayService.deactivate() instead.
  • isActivated(): use DisplayServiceManager.INSTANCE.getMode() == DisplayMode.NORMAL instead.
  • isCollapse(): use isCollapsed() instead.
  • isVisibleForFilters(): use getAppliedFilters() instead.
  • isVisible(): use DisplayService.isDisplayed() instead.
  • isFiltered(), isNotFiltered(), isVisibleForActivatedFilters(), @checkFilters(): use getAppliedFilters() and DDiagram.getActivatedFilters() instead.
• The deprecated methods isDirectlyHidden() and isIndirectlyHidden() in HideFilterHelper have been removed. Use the corresponding methods in DDiagramElementQuery instead.
• The deprecated method SavingPolicy.save(Iterable, Map) has been removed. Use the variant which takes an additional IProgressMonitor instead.
• The deprecated constructor AbstractCommandFactory(TransactionalEditingDomain, ModelAccessor) has been removed. Use the variant without the ModelAccessor argument instead.
• The deprecated constructor CommandContext(EObject) has been removed. Use the variant which takes an additional DRepresentation instead.
• The deprecated methods activate(TransactionalEditingDomain) and deactivate(TransactionalEditingDomain) in IChangeListener have been removed. Use the variants with no argument instead.
• The deprecated constructor AddSemanticResourceCommand(Session, URI) has been removed. Use the variant which takes an additional IProgressMonitor instead.
• The deprecated constructors of RemoveSemanticResourceCommand have been removed. Use the variants which takes an additional IProgressMonitor instead.
• The deprecated constructor in CreateDiagramWithInitialOperation has been removed. Use the variant which takes an additional IProgressMonitor instead.
• The deprecated method SessionManager.addResource(Session, Resource) has been removed. Use the Session.addSemanticResource(URI, IProgressMonitor) instead. In code, mySessionManager.addResource(mySession, myResource) should be replaced by mySession.addSemanticResource(myResource.getURI(), new NullProgressMonitor()). Notice that this replacement has not the exact same behavior. The notifications SessionListener.ABOUT_TO_BE_REPLACED and SessionListener.REPLACED are not thrown with addSemanticResource contrary to addResource. But this kind of notifications is more for reloading of resource.
• The deprecated constructor of DefaultLocalSessionCreationOperation have been removed. Use the variant which takes an additional IProgressMonitor instead.
• The deprecated method SessionManager.getSession(URI) has been removed. Use the variant which takes an additional IProgressMonitor instead.
• The deprecated method SessionFactory.createSession(URI) has been removed. Use the variant which takes an additional IProgressMonitor instead.
• Deprecated class RefreshRepresentationCommand has been removed. Use the class RefreshRepresentationsCommand instead.
• Deprecated classes RevealSiriusElement and RevealDDiagramElement have been removed. Use the class RevealDDiagramElements instead.
• The deprecated method DAnalysisSession.save(Map<?, ?>) has been removed. Use the variant which takes an additional IProgressMonitor instead.
• The deprecated method MappingTableEntry.getImporter() has been updated. It now returns an optional ( org.eclipse.sirius.common.tools.api.util.Option) of MappingTableEntry.
• The deprecated class IEMFCommandFactory has been removed. It is not used in Sirius code anymore.
• The deprecated method IDiagramCommandFactory.buildCreateDiagramFromDescription(DiagramDescription, EObject) has been removed. Use the variant which takes an additional IProgressMonitor instead.
• The deprecated methods dispose() and disposeInterpreterRegistry(EObject) have been removed from InterpreterRegistry. They corresponded to dead code.
• The deprecated method InterpreterRegistry.prepareImportsFromModelElement(IInterpreter, EObject) has been removed. Use InterpreterRegistry.prepareImportsFromSession(IInterpreter, Session) instead. To get Session from EObject, you can use SessionManager.INSTANCE.getSession(EObject).
• The deprecated method SiriusHelper.createDAnalysis() has been removed. Use ViewpointFactory.eINSTANCE.createDAnalysis() instead.
• The deprecated method SessionFactory.createSession(DAnalysis) has been removed. It is not intended to be used, but it can be replaced by SessionFactory.INSTANCE.createSession(analysis.eResource().getURI(), new NullProgressMonitor()).
• The method buildDoExecuteDetailsOperation(DSemanticDecorator, RepresentationCreationDescription, String) has been pull up from @ITableCommandFactory, ITreeCommandFactory and IDiagramCommandFactory to ICommandFactory.
• The method getUserInterfaceCallBack() has been pull up from ITableCommandFactory and ITreeCommandFactory to ICommandFactory. And AbstractCommandFactory now implements this method.
• The unused reference allActivatedEdgeMappings from Layer and DiagramDescription has been removed from the viewpoint.ecore meta-model. This reference always returns empty list.

Changes in org.eclipse.sirius.diagram

• The deprecated methods IDiagramEdgeEditPart.refreshPath() and AbstractDiagramEdgeEditPart.refreshPath() have been removed. It is not called in Sirius code anymore

Changes in org.eclipse.sirius.ecore.extender

• The deprecated methods IMetamodelExtender.eDelete(EObject), CompositeMetamodelExtender.eDelete(EObject) and ModelAccessor.eDelete(EObject) have been removed. Use the variants which takes an additional ECrossReferenceAdapter instead. This ECrossReferenceAdapter can be null.

Changes in org.eclipse.sirius.ui

• All deprecated methods in ModelingProjectManager have been removed. Use the corresponding versions which take an additional IProgressMonitor parameter instead.
• All deprecated methods in ViewpointSelection have been removed. Use the corresponding versions which take an additional IProgressMonitor parameter instead.
• Deprecated class org.eclipse.sirius.ui.business.api.control.SiriusControlCommand has been removed. Use the class org.eclipse.sirius.business.api.control.SiriusControlCommand instead (same constructor but with an additional IProgressMonitor parameter).
  • Ditto for SiriusUnControlCommand
• The deprecated method DialectUIServices.openEditor(Session, DRepresentation) has been removed. Use the variant which takes an additional IProgressMonitor instead.
• The deprecated method SessionHelper.openStartupRepresentations(Session) has been removed. Use the variant which takes an additional IProgressMonitor instead.
• The deprecated method SiriusControlHandler.performControl(Shell, EObject) has been removed. Use the variant which takes an additional IProgressMonitor instead.
• The deprecated method SiriusUncontrolHandler.performUncontrol(Shell, EObject) has been removed. Use the variant which takes an additional IProgressMonitor instead.
• New class AbstractCreateRepresentationFromRepresentationCreationDescription: Generalization of all CreateRepresentationFromRepresentationCreationDescription classes (iof plug-ins sirius.diagram, sirius.table.ui, sirius.tree.ui).

Changes in org.eclipse.sirius.table

• The deprecated method TableHelper.getCell(DLine, String) has been removed. Use the variant which take a DLine and a DColumn as parameters.

Changes in org.eclipse.sirius.tree

• The deprecated method DTreeUserInteraction.refreshContent() has been removed. Use the variant which take an additional IProgressMonitor parameter instead.

Changes in Sirius 0.9.0

Version 0.9.0 is the first release under the Sirius name and under the Eclipse Foundation umbrella. Except for the few cases mentioned below (in the “Other API Changes”, “Specifier-Visible Changes” and “User-Visible Changes” sections), Sirius 0.9.0 is functionally equivalent to the latest version of Viewpoint (version 6.10), which was the name of the project before it was open sourced at Eclipse. See the rest of the documentation for the complete list of feature of the Sirius platform.

Migrating from Obeo Designer or Viewpoint to Sirius

If you have existing projects which used this technology before it became Eclipse Sirius and want to migrate to Sirius, you must:

1. first migrate your projects and models to the latest pre-Sirius version of Viewpoint or Obeo Designer available to you (Viewpoint is the previous name of Sirius);
2. then migrate those to Sirius 0.9.

The latest version of Viewpoint which was available in an Obeo Designer release is Viewpoint 6.8, released in Obeo Designer 6.2. Sirius 0.9 is based on Viewpoint 6.10, which was not released publicly.

If you were using Obeo Designer, you must thus first migrate your projects and models to Obeo Designer 6.2, and then consult the release notes for Viewpoint 6.9 and 6.10, which lists the API changes from Viewpoint 6.8 to 6.10.

Once your projects are compatible with the latest Viewpoint available to you, you can migrate to Sirius, first by updating your Viewpoint Specification Projects and plug-ins which use the Viewpoint APIs, then by updating any Modeling Project and representation files ( *.aird).

Migrating Viewpoint Specification Projects

• Any plug-in dependencies towards Viewpoint plug-ins must be updated to the corresponding Sirius plug-in and version number. See the correspondence table below for the plug-in names to use.
• If your plug-ins used any of the extension points defined in Viewpoint, you will need to update your plugin.xml files to reference the correct extension points identifiers. In particular, all Viewpoint Specification Projects created using Viewpoint use the fr.obeo.dsl.viewpoint.componentization in their plugin.xml to register the VSMs they define. This should be changed to use the equivalent org.eclipse.sirius.componentization extension point id. The identifier changes for the other extension points follow the same rules as the name changes of the plug-ins they are defined in.
• The migration of your VSMs ( *.odesign files) is automatic: simply open your files once in the VSM editor, perform some no-op change to make the editor “dirty” and save it. The saved version will have been migrated to Sirius.
• If you had Java code which used the Viewpoint APIs, you will need to update it to use the Sirius APIs. A simple “Source > Organize Imports” on your source folders should find most classes you used in their new namespace. The Viewpoint code base and APIs used the term “Viewpoint” both for the name of the product and for the name of the concept. When it refered to the name of the product, the names were changed to use “Sirius” instead, so you may need to adjust some names in your code beyond just updating the imports (for example, ViewpointControlCommand is now SiriusControlCommand).

Note that if you used Obeo Designer, you may have used the legacy Acceleo 2.x language for the computed expressions inside the *.odesign files (if your expressions are of the form <%something%> then you used the legacy language). That language is not supported anymore in Sirius 0.9, so you must migrate your expressions to use Acceleo 3 and/or the specialized interpreters ( var:, feature: and service:, see the documentation).

Migrating Modeling Projects and Representation Files

• First migrate any modeler definitions used by your modeling projects and representation files (see the section above).
• Modeling projects created using Viewpoint will not be recognized directly by Sirius, because the nature identfier has changed. You must use the “Configure/Convert to Modeling Project” action in the project’s context menu to make it a Sirius-compatible modeling project (see the section below for the technical details of the change).
• The migration of you representation files ( *.aird) is performed automatically when they are loaded in memory. It will become permanent the first time you save it (you can force this by opening a representation, making some arbitrary change and saving the session).

Plug-ins version numbers.

As of Sirius 0.9, and probably at least until Sirius 1.0 when the APIs will be more stable, all the bundles share the same version, which is also the version for the feature. If you used versioned dependencies to the old Viewpoint code (e.g. dependencies towards Viewpoint 6.8), you need to adjust the versions in your MANIFEST.MF files in addition to the namespaces.

Major namespace changes

In the context of the move as an official Eclipse project named Sirius, all the namespaces used in the code have changed.

Plug-in and features identifiers

All identifiers have changed to start with the org.eclipse.sirius namespace prefix. The tables below give the mapping between the Viewpoint plug-in and features identifiers and their Sirius equivalent.

Java Packages and Classes Names

The Java package names have changed to start with the identifier of the plug-in they are defined in (which has changed). A simple “Source > Organize Imports” on your source folders should find most classes you used in their new namespace.

The Viewpoint code base and APIs used the term “Viewpoint” both for the name of the product and for the name of the concept. When it refered to the name of the product, the names where changed to use “Sirius” instead (for example, ViewpointControlCommand is now SiriusControlCommand).

Models namespace URIs

All namespace URIs have also been changed from “http://www.obeo.fr/dsl/viewpoint*” to “http://www.eclipse.org/sirius/”.

If you have created VSM file (.odesign) or representations file (.aird) with Viewpoint, the changes of the namespace URIs will be automatically migrated during the loading of your VSM or your representations file. These new nsURIs will be stored physically in the file during the first save. If the file is not saved, the automatic migration will be replayed at the next opening.

Nature ID

The modeling project has a specific nature ( org.eclipse.sirius.nature.modelingproject).
If you have modeling project created with Viewpoint, you must launch the action “Configure/Convert to Modeling Project” to replace old nature id ( fr.obeo.dsl.viewpoint.nature.modelingproject) by the new one.
If you have many modeling projects to “migrate”, you can easily make a script to replace fr.obeo.dsl.viewpoint.nature.modelingproject by org.eclipse.sirius.nature.modelingproject in all .project file of each modeling projects.

Other API Changes

This section only lists API changes in Sirius 0.9.0 compared to the latest version of Viewpoint it is based on, i.e. Viewpoint 6.10.

API Added

• Add IMigrationParticipant.getPackage() to return the EPackage to use for the given namespace. This change concerns our internal migration framework. This is useful to handle our namespace changes (from Viewpoint to Sirius).

API Removal

• Removed org.eclipse.sirius.common.tools.api.interpreter.IAcceleoInterpreterVariables: This interface only defined a single constant, which refered to the syntax of an obsolete version of the Acceleo language.
• Removed org.eclipse.sirius.common.tools.api.resource.IFileContributorExtension: This interface only defined a few constants relative to an extension point which does not exist anymore.
• Removed the org.eclipse.sirius.reconciler extension point definition (which used to be defined in the org.eclipse.sirius plug-in): This extension point is not supported anymore (and has not been for a long time).
• Removed all the deprecated methods from Session and replaced the internal calls with the equivalent versions with IProgressMonitors. The removed methods are:

void open();
void addSemanticResource(Resource newResource, boolean addCrossReferencedResources);
void addSemanticResource(URI semanticModelURI, boolean addCrossReferencedResources);
void addSemanticResource(URI semanticModelURI, boolean addCrossReferencedResources, IProgressMonitor monitor);
void removeSemanticResource(Resource resource, boolean removeCrossReferencedResources);
void removeSemanticResource(Resource semanticResource);
void save();
void close();
Collection<Viewpoint> getSelectedViewpoints();
void createView(Viewpoint viewpoint, Collection<EObject> semantics);
void createView(Viewpoint viewpoint, Collection<EObject> semantics, boolean createNewRepresentations);
void addSelectedView(DView view) throws IllegalArgumentException;
void removeSelectedView(DView view);

Specifier-Visible Changes

New variables are available for sizeComputationExpression to compute the size of edges on EdgeStyleDescription and BracketEdgeStyleDescription:

• diagram: the current DDiagram
• view: the current DEdge
• sourceView: the source view of the current edge.
• targetView: the target view of the current edge.

User-Visible Changes

• The ability to print table representations has been disabled for the 0.9 release due to an external dependency issue (see bug #422223: for the details). It should be re-introduced in 1.0.