Changes between Version 16 and Version 17 of Migration_of_MSPlugins


Ignore:
Timestamp:
11/14/2016 07:53:20 PM (4 years ago)
Author:
sena
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Migration_of_MSPlugins

    v16 v17  
     1== General migration notes ==
     2
     3Here is the check-list of items for migrating the plugins to E4:
     4
     5- no plugin should contain a dependency to org.eclipse.ui package: removal of this dependency sometimes requires the addition of org.eclipse.jface dependency
     6- all editors/views/commands (part of GUI - originally in plugin.xml) should become a POJO
     7- Activators that extend AbstractUIPlugin (which is part of eclipse.ui) should be converted to implement BundleActivator instead
     8- All gui related items should be defined in fragment.4xmi instead of plugin.xml, propertyreader extension should still be in plugin.xml
     9- Since only the parts/objects that are created through the context can use injected variables/objects/services, these classes should be defined in fragment.4xmi or created by ContextInjectionFactory.make(...) in any part of the code. "AddOn" can be used to inject utility classes (which require access to injected variables like workspace_location for example) into the context at startup
     10
     11
    112== List of MS plugins migrated ==
    213