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.
Difference between revisions of "EEF/Migrating version"
< EEF
(→Migrating @runtime) |
(→Migrating from end-user point of view) |
||
Line 22: | Line 22: | ||
− | *Finally, update the OpenWizardOnDoubleClick constructor | + | *Finally, '''update the OpenWizardOnDoubleClick constructor cal'''l (if you use wizards). It takes now the adapterFactory to use in parameter. |
[[Image:EEF_0.9_Migrating_-_Add_AdapterFactory_to_OpenWizardOnDoubleClick_listener_constructor.png|Add adapterFactory to OpenWizard listener constructor]] | [[Image:EEF_0.9_Migrating_-_Add_AdapterFactory_to_OpenWizardOnDoubleClick_listener_constructor.png|Add adapterFactory to OpenWizard listener constructor]] | ||
Revision as of 06:39, 6 January 2011
This page list all the migration process
Contents
From v0.8.X to v0.9.X
Migrating models
There was no regressive changes in EEF metamodels in 0.9 version.
Migrating from end-user point of view
- First, relaunch generation. Use the organize imports action of JDT if needed.
- If you have user code lost in *.lost files, use components and views extension mechanism to reintegrate this code. Delete lost files.
- The components providing mechanism have been changed in 0.9. EEF don't use the XXXPackageEditionProvider and XXXPackagePolicyEditionProvider to get controller and editing policies but a generated AdapterFactory instead. Delete theses classes.
- The sample plugin.xml generated file is updated with the new AdapterFactory declaration. Replace old EEF providers declaration by the generated AdapterFactory.
- Finally, update the OpenWizardOnDoubleClick constructor call (if you use wizards). It takes now the adapterFactory to use in parameter.