|
| Re: migrating from Obeo to Sirius [message #1404466 is a reply to message #1404436] |
Fri, 01 August 2014 14:25   |
|
Hi Nassim,
You can directly migrate your OD 6.2 project(s) toward Sirius 1.0 by
following all the steps from “Changes in Sirius 0.9.0” to “Changes in
Sirius 1.0.0 (from Sirius 1.0.0M7)”.
(https://www.eclipse.org/sirius/doc/Release%20Notes.html).
The release note is a quite confusing since it contains all necessary
informations about API changes, new namespaces etc. That concerns users
who wrote some code depending on the old Viewpoint API (it's maybe your
case).
But if your project(s) just consists in Viewpoint Specification
Project(s) (with *.odesign) and Modeling project(s) (with*.aird files
and your model(s)), the migration is automatic for them.
Paragraphs bellow are extract from
https://www.eclipse.org/sirius/doc/Release%20Notes.html#sirius0.9:
Migrating Viewpoint Specification Projects
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.
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: andservice:, 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).
Regards,
Florian
On 08/01/2014 01:54 PM, Nassim Jibai wrote:
> Hello Everyone,
>
> I am trying to migrating from Obeo designer 6.2 to Sirius 1.0. Does
> anyone please know a site where a procedure describing how this
> migration is done. Mainly, the equivalent plug-in from Obeo to Sirius. I
> read on this site
> http://www.eclipse.org/sirius/doc/Release%20Notes.html#sirius0.9
> that the steps are to start the migration to sirius 0.9 and then go up
> the chain. But this is quite confusing. I am using the new eclipse luna
> where Sirius 1.0 is pre-installed and Im using along it uml2 designer.
> Any help will be very appreciated.. :)
> Thank you in advance,
> NJ
|
|
|
|
| Re: migrating from Obeo to Sirius [message #1404603 is a reply to message #1404580] |
Mon, 04 August 2014 12:35 |
|
Hi Nassim,
Unfortunately we don't provide any automatic action to migrate java code
depending on the old viewpoint API. An Eclipse “organize imports”can
resolve much of the classes that have just been moved to the new sirius
namespaces. Other API changes like classes renamed or methods changes
have to be done manually. (a lot of classes containing
“(...)Viewpoint(...)” have been renamed into (...)Sirius(...) when
Viewpoint referred to the product name).
Regards
Florian
On 08/04/2014 11:34 AM, Nassim Jibai wrote:
> Hello Florian,
> Thank you so much for this reply. I was wondering if there are any
> scripts or batch that overlap or convert these api automatically?
> regards,
> Nassim
|
|
|
|
|
|
|
| Re: migrating from Obeo to Sirius [message #1404969 is a reply to message #1404961] |
Wed, 06 August 2014 09:10 |
|
Le 06/08/2014 10:44, Nassim Jibai a écrit :
> Thank you so much for the reply and all the link.. :) I have another
> question: Is there a table describing where i can find the equivalent
> classes of Obeo
[side note: "Obeo" is the name of the company, the product is "Obeo
Designer"]
If you want this to migrate your code, note that once the Sirius 0.9
plug-ins are correctly referenced by your own plug-ins, the automatic
"Organize import" of JDT launched on the project root will take care of
99% of the renamings.
> in Sirius 0.9? The table in
> http://www.eclipse.org/sirius/doc/Release%20Notes.html#sirius0.9 only
> describes the plugins..
The only changes between Obeo Designer 6.2 and Sirius 0.9 are:
- the plug-in names (the table you mention gives the equivalences)
- the package names of the classes inside the plug-ins. The equivalences
follow the same rules as the plug-ins, as in general all packages in a
plugin start with the name of the plug-in, i.e. all Java packages inside
the fr.obeo.dsl.viewpoint.diagram plug-in (in Obeo Designer) are of the
form fr.obeo.dsl.viewpoint.diagram.something; the corresponding package
in Sirius 0.9 can be found simply by replacing the prefix part
corresponding to the plug-in name.
- some classes (and methods) in Obeo Designer used the name "Viewpoint"
as the name of the product (instead of the concept of "point of view"),
and thus have been renamed to use Sirius (the new project name). For
example "ViewpointDiagramEditor", in addition to having been moved into
an org.eclipse.sirius namespace, has been renamed SiriusDiagramEditor.
So basically if you have the simple class name on the Obeo Designer
side, Navigate > Open Type... (Ctrl+Shift+t) and enter
"org.eclipse.sirius*TheClassName" and Eclipse should find it. If the
class contains "Viewpoint" in its name and you don't find the Sirius
equivalent, try replacing the "Viewpoint" part with "Sirius".
Regards,
Pierre-Charles David
Pierre-Charles David - Obeo
Need training or professional services for Sirius?
http://www.obeodesigner.com/sirius
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03591 seconds
] 
Search
Help
Register
Login
Home
