syncope-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Francesco Chicchiriccò <>
Subject [DISCUSS] Replace Activiti with Flowable?
Date Tue, 21 Feb 2017 19:31:35 GMT
Hi all,
I have been recently made aware that many of the original developers of 
Activiti (including the team leader Tijs Rademakers) started a new fork, 
Flowable [1].
The detailed reasons for forking can be read from [2] but, besides 
these, I think we need to decide whether to stick with Activiti as our 
predefined workflow engine, or if instead it is be the case to move to 

It seems that one of the main reasons behind the fork is the fact that 
the original team wasn't able to cut out the new 6.0.0 release (which is 
being worked since long time); the new team has recently published 6.0.0 
[3] and also a maintenance 5.22.0 [4] (which is the version we are 
currently using, but from Activiti).

Flowable 6 looks really interesting, especially for the cleaning and the 
refactoring they made - which also solved the issue raised a while ago 
in [5] about the Activiti Modeler license: it seems that the new 
Flowable UI Modeler is completely AL 2.0 compliant; moreover, they 
introduced some interesting support for multi-tenancy [6] which we can 

I would propose to:

 1. open an issue to make the 2.1 series (e.g. the current master
    branch) work with Flowable 6, replacing Activiti
 2. open an issue to provide an additional module for the 2.0 series
    (e.g. the current 2_0_X branch), named workflow-flowable, mostly a
    clone of workflow-activiti [7] but with different dependencies;
    workflow-activiti will remain the default choice, but people could
    switch to Flowable on their own deployments if they will



Francesco Chicchiriccò

Tirasa - Open Source Excellence

Member at The Apache Software Foundation
Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message