You are required to read and agree to the below before accessing a full-text version of an article in the IDE article repository.

The full-text document you are about to access is subject to national and international copyright laws. In most cases (but not necessarily all) the consequence is that personal use is allowed given that the copyright owner is duly acknowledged and respected. All other use (typically) require an explicit permission (often in writing) by the copyright owner.

For the reports in this repository we specifically note that

  • the use of articles under IEEE copyright is governed by the IEEE copyright policy (available at
  • the use of articles under ACM copyright is governed by the ACM copyright policy (available at
  • technical reports and other articles issued by M‰lardalen University is free for personal use. For other use, the explicit consent of the authors is required
  • in other cases, please contact the copyright owner for detailed information

By accepting I agree to acknowledge and respect the rights of the copyright owner of the document I am about to access.

If you are in doubt, feel free to contact

Get EPF Composer back to the future: A trip from Galileo to Photon after 11 years

Publication Type:

Article, research overeview


EclipseCon France2018


This talk provides a concrete return of experience about the migration of Eclipse Process Framework (EPF) Composer[i] from Eclipse Galileo 3.5.2 to Eclipse Neon 4.6.3. The migration of EPF Composer was performed[ii] in four phases:compatible versions of required softwares were installed from the Neon software repository and then deprecations in the source code were analyzed and fixed; scheduling conflicts were resolved for the persistence of method elements (i.e., method configurations, method plugins, method content descriptions and processes) in their own folders and XMI files; appearance and height problems were resolved for the combo box which supports users in selecting the currently used method configuration, the blank views were removed from the authoring and browsing perspectives, but also problems with the rich text editor were resolved for enabling users to format and style text; and incompatible bundles were removed from the feature plugins, replacing bundles were added and other missing dependencies for the bundles were resolved for exporting the standalone application. This talk will also present the return of experience of starting a collaboration with the EPF Composer team from IBM in order to submit the migrated code, eventually become a committer of the project, and publish a release of EPF Composer for Eclipse Neon.More about the Eclipse Process Framework:The EPF Composer is an open-source project developed for the process engineers and project managers. It provides support for authoring, tailoring and deploying methods and processes for development organizations and projects. Although this project has attracted considerable attention from researchers and practitioners worldwide, the migration to newer versions of technologies was never performed.In the context of the AMASS project[iii], the migration of EPF Composer was critical for allowing the integration with other tools in the AMASS platform, a large open-source platform that constitutes an ecosystem building on top of several Eclipse and PolarSys projects such as EPF Composer, OpenCert[iv] and CHESS[v].The migration of EPF Composer has been tested by Vishal Sharnagat (IBM). Barbara Gallina and Muhammad Atif Javed would also like to thank Bruce MacIsaac (IBM), Huascar Espinoza (Tecnalia) and Gaël Blondelle (Eclipse Foundation) for their support in the migration. As future work, we plan to implement the support for CDO model repository[vi]. [i][ii][iii][iv][v][vi]


author = {Muhammad Atif Javed and Barbara Gallina},
title = {Get EPF Composer back to the future: A trip from Galileo to Photon after 11 years},
month = {June},
year = {2018},
journal = {EclipseCon France2018},
url = {}