Eclipse Community Forums: Eclipse Scout » Guide line to migrate from Kepler to Oxygen

Help

Home

Home » Eclipse Projects » Eclipse Scout » Guide line to migrate from Kepler to Oxygen(Oxygen 7.0)

Show: Today's Messages :: Show Polls :: Message Navigator

Guide line to migrate from Kepler to Oxygen [message #1781891]

Wed, 14 February 2018 11:02

marco giudici

Messages: 204
Registered: February 2013
Location: Italy

Senior Member

Good morning to all,
I have an old application developed with Eclipse Kepler with Scout 3.9 and now I need to migrate on Oxygen 7.0
First of all is it possible do this type of migration or is necessary rewrite everythink with Oxygen?
If the migration is possible there is a tool or function that help in this task?
What are the guide line to follow during the migration?

Thanks in advance for any help

Report message to a moderator

Re: Guide line to migrate from Kepler to Oxygen [message #1781898 is a reply to message #1781891]

Wed, 14 February 2018 11:41

Patrick Baenziger

Messages: 96
Registered: September 2011

Member

Hello Marco

Basically, yes, you can migrate between from your version to Oxygen.
Such a big version jump will however require a significant amount of changes. Some part of migrations between versions might also be unnecessary because we switched to the HTML-Renderer in Scout 6.0.

Your migration path (relevant changes) would be:
3.9 -> 4.0 -> 5.0 -> 6.0 -> 7.0

Depending on the size of your application, it can be easier to start from a new, empty application template from Scout 7.0 (Oxygen) and copy&migrate code from your old application into it. This is probably the fastest way to do it.

There is no tooling or SDK support for this kind of migration.
Since version 6.0, we offer an incremental Migration Guide on the Documentation Page (see "All Releases" -> ... -> Migration Guide): Documentation Page

For the previous versions, please see the "New and Noteworthy" pages:

Report message to a moderator

Re: Guide line to migrate from Kepler to Oxygen [message #1781899 is a reply to message #1781898]

Wed, 14 February 2018 11:46

marco giudici

Messages: 204
Registered: February 2013
Location: Italy

Senior Member

Hi Patrick,
thank you very much for your explanation and suggestion about how to do this migration.
I check all your links and if I have other questions came back here.

Thanks

Report message to a moderator

Re: Guide line to migrate from Kepler to Oxygen [message #1782645 is a reply to message #1781899]

Tue, 27 February 2018 10:57

Urs Beeli

Messages: 573
Registered: October 2012
Location: Bern, Switzerland

Senior Member

Hi Marco

We migrated four large business applications from Scout 5.0 to Scout 6.1 about a year ago. In my experience, the MIgration Guides (5.0 -> 6.0 & 6.0 -> 6.1) as well as the new technical reference made this relatively easy. [1]

The main aspects that caused changes were:

replacement of deprecated methods (since you will be coming from 3.9, you will probably have more effort here than we did, coming from 5.0)
adjustment for changed package and class names -> trivial search and replace
adjustment for changed service registry (BEANS.get instead of SERVICES.getService) -> trivial search and replace
adjustment for new jobs api (some major code rewrites, but documentation made this fairly easy)
change to web based application (second server instance, change in configuration etc) -> probably best to create a new project using the latest scout version and use that as a basis
migration of custom formfields (SWT --> HTML5), if you don't have custom widgets you can skip this :-)

All in all, the transition was relatively smooth.

We have not yet gone to 7.0, but the documents we used also exist for that version:

[Updated on: Tue, 27 February 2018 11:14]

Report message to a moderator

Previous Topic:	[Oxygen] Wizard - CanFinish or disable Finish-Button
Next Topic:	Group-wise filter rows in table

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Tue Apr 23 06:28:12 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter