Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Sirius/1.0.0M7"

m (New & Noteworthy)
(New & Noteworthy)
Line 31: Line 31:
 
== New & Noteworthy ==
 
== New & Noteworthy ==
  
* #430527: We fixed all packaging issues identified by the automated reports which were launched on M6. In particular our update-sites now include pack200 versions of our JARs.
+
The most important changes in this milestone are:
* #428322, #431634: The dynamic tabbar work, which was disabled by mistake in M6, will finally be visible in M7. This allowed us to find (and fix) a memory leak in the platform, which will also by released in M7.
+
* #428322, #431634: The dynamic tabbar work, which was disabled by mistake in M6, are finally visible in M7. This allowed us to find (and fix) a memory leak in the platform, which will also by released in M7.
 
* #427803: The metamodel and associated code for the diagram dialect has now been completely moved out of the core of Sirius itself.
 
* #427803: The metamodel and associated code for the diagram dialect has now been completely moved out of the core of Sirius itself.
* #430263: Starting with M7, Sirius will no longer automatically start and load itself as soon as Eclipse is launched, but instead will be loaded only when it starts to be used. This will improve the startup time of the Eclipse Modeling Package (among others).
 
* #431132, #431133, #430536: Various improvements in the way we manage the target platforms used to build Sirius. They should enable a better control on what we depend on and better/earlier visibility on potential integration issues.
 
 
* #429682: We had to change some of our APIs (with no loss of functionality) to avoid exposing Guava-specific types. See the bugzilla (and the related #428976) for the technical details, but the end result is better compatibility with the other components of the release train (and ecosystem at large).
 
* #429682: We had to change some of our APIs (with no loss of functionality) to avoid exposing Guava-specific types. See the bugzilla (and the related #428976) for the technical details, but the end result is better compatibility with the other components of the release train (and ecosystem at large).
* #427247: Cleanup of our metamodels by removing very old and unsupported parts. While each of these are technically API changes, they should have very little impact on most users. If you rely heavily on the Sirius meta-models in your code, please see the details in the bugzilla about the actual changes, and the release notes which explain how to adapt your code when relevant. Note that this is actually a rather large task, only parts of which will be done in M7.
+
* #430263: Starting with M7, Sirius no longer automatically starts and loads itself as soon as Eclipse is launched, but instead is loaded only when it starts to be used. This improves the startup time of the Eclipse Modeling Package (among others).
* #431359: For historical reasons, the definition of the Sirius session resources (the aird files) was done in the diagram-specific plug-ins. This can cause issues when only the core of Sirius but not the diagram-specific parts are installed. This issue is about moving this definition back into the core. The related #427017 tries to remove a costly GMF-specific adapter on aird resources.
+
* #430527: We fixed all packaging issues identified by the automated reports which were launched on M6. In particular our update-sites now include pack200 versions of our JARs.
* #432021: Sirius installs some of its (layout) providers too broadly, which causes issues when using other GMF-based tools (e.g. Papyrus) if Sirius is installed.
+
* #431132, #431133, #430536: Various improvements in the way we manage the target platforms used to build Sirius. They should enable a better control on what we depend on and better/earlier visibility on potential integration issues.
* #430495, #432931: better support for XText-based models.
+
* #427247: Cleanup of our metamodels by removing very old and unsupported parts. While each of these are technically API changes, they should have very little impact on most users. If you rely heavily on the Sirius meta-models in your code, please see the details in the bugzilla about the actual changes, and the release notes which explain how to adapt your code when relevant. Note that this is actually a rather large task, only parts of which will are included in M7.
 +
* #431359: For historical reasons, the definition of the Sirius session resources (the aird files) was done in the diagram-specific plug-ins. This can cause issues when only the core of Sirius but not the diagram-specific parts are installed. The resource definitions and implementations have moved into the core org.eclipse.sirius plug-in itself to ensure they are always available. Note that at the moment this means org.eclipse.sirius depends on parts of GMF; we will try to remove this dependency for 1.0.
 +
* #432021: Sirius installs some of its (layout) providers too broadly, which causes issues when using other GMF-based tools (e.g. Papyrus) if Sirius is installed. We are now more careful about this and do not interfere with other GMF-based modelers.
 +
* #430495, #432931: better support for XText-based models, in particular when it comes to XText DSLs which integrate with Java.
 
* #430579: better defaults in Tree dialect to avoid performance issues.
 
* #430579: better defaults in Tree dialect to avoid performance issues.
 
These are either not started yet or not in an advanced state but are important bugfixes or improvements that we'll do our best to include before M7:
 
* #432986: This is a loss of functionality as a side-effect of moving the diagram dialect out of the core. We understand what happened and how to fix it, but have not started working it yet.
 
  
 
See [http://eclipse.org/sirius/doc/Release%20Notes.html#sirius1.0M7 the release notes] for details about API changes.
 
See [http://eclipse.org/sirius/doc/Release%20Notes.html#sirius1.0M7 the release notes] for details about API changes.

Revision as of 08:41, 5 May 2014

THIS IS A DRAFT

Sirius 1.0.0M7 is a milestone release which has been included in Luna M7. The project is still in incubation at this time.

TBD: See also [TBD the announce on the mailing list].

Availability

Sirius 1.0.0M7 was released on 2014-04-12 (tag v1.0.0M7, commit XXXX). It is available from the following update sites:

It is recommended you use the update-site matching the version of Eclipse you use to avoid potential issues at runtime.

If you want to install the new org.eclipse.sirius.tests feature, which provides APIs to help create automated tests of Sirius-based modelers, you will need to add the following update-site:

Juno users: Sirius depends on more recent versions of some components that what is available by default from a Juno install. You need to add the following update-sites if you want to install Sirius 1.0.0M7 on Juno:

Compatibility

Sirius 1.0.0M7 is compatible with the following versions of Eclipse:

  • Eclipse 3.8/4.2 (Juno)
  • Eclipse 4.3 (Kepler)
  • Eclipse 4.4M7 (Luna)

New & Noteworthy

The most important changes in this milestone are:

  • #428322, #431634: The dynamic tabbar work, which was disabled by mistake in M6, are finally visible in M7. This allowed us to find (and fix) a memory leak in the platform, which will also by released in M7.
  • #427803: The metamodel and associated code for the diagram dialect has now been completely moved out of the core of Sirius itself.
  • #429682: We had to change some of our APIs (with no loss of functionality) to avoid exposing Guava-specific types. See the bugzilla (and the related #428976) for the technical details, but the end result is better compatibility with the other components of the release train (and ecosystem at large).
  • #430263: Starting with M7, Sirius no longer automatically starts and loads itself as soon as Eclipse is launched, but instead is loaded only when it starts to be used. This improves the startup time of the Eclipse Modeling Package (among others).
  • #430527: We fixed all packaging issues identified by the automated reports which were launched on M6. In particular our update-sites now include pack200 versions of our JARs.
  • #431132, #431133, #430536: Various improvements in the way we manage the target platforms used to build Sirius. They should enable a better control on what we depend on and better/earlier visibility on potential integration issues.
  • #427247: Cleanup of our metamodels by removing very old and unsupported parts. While each of these are technically API changes, they should have very little impact on most users. If you rely heavily on the Sirius meta-models in your code, please see the details in the bugzilla about the actual changes, and the release notes which explain how to adapt your code when relevant. Note that this is actually a rather large task, only parts of which will are included in M7.
  • #431359: For historical reasons, the definition of the Sirius session resources (the aird files) was done in the diagram-specific plug-ins. This can cause issues when only the core of Sirius but not the diagram-specific parts are installed. The resource definitions and implementations have moved into the core org.eclipse.sirius plug-in itself to ensure they are always available. Note that at the moment this means org.eclipse.sirius depends on parts of GMF; we will try to remove this dependency for 1.0.
  • #432021: Sirius installs some of its (layout) providers too broadly, which causes issues when using other GMF-based tools (e.g. Papyrus) if Sirius is installed. We are now more careful about this and do not interfere with other GMF-based modelers.
  • #430495, #432931: better support for XText-based models, in particular when it comes to XText DSLs which integrate with Java.
  • #430579: better defaults in Tree dialect to avoid performance issues.

See the release notes for details about API changes.

The complete list of bugs fixed in this version can be seen on Bugzilla.

Back to the top