Bug 527280 - Consider deprecating External Java Actions
Summary: Consider deprecating External Java Actions
Status: NEW
Alias: None
Product: Sirius
Classification: Modeling
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2017-11-15 02:48 EST by Pierre-Charles David CLA
Modified: 2017-11-17 04:49 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Pierre-Charles David CLA 2017-11-15 02:48:10 EST 
External Java Actions is one of the mechanisms that can be used to define parts of a Sirius modeler in plain Java. However it is less flexible than the alternative, Java services. In particular External Java Actions require registering an extension and launching an Eclipse runtime to test it. Having two separate mechanisms can also be confusing and adds maintenance (and documentation, and testing overhead).

We should review which use cases of External Java Actions can not currently be covered by other mechanisms (including, but not limited to, Java services). If there are none, they can probably be deprecated (with some migration path at least documented, or even automated if possible). If there are legitimate use cases that only EJAs currently support, we should consider improving other mechanisms to cover them, and only then deprecate EJAs.