Fusion: investigate how to split Fusion and Flow

Split Fusion and Flow has been a recurring topic from time to time, but not really much has been done. Let’s try to make it happen by starting from this investigation ticket.

The expected outcome: A document about the findings and proposal(s). No need to touch the code, we will decide what to do based on the findings.

Fusion codes are in 4 modules in Flow:

1. fusion-endpoint, which is pure fusion, should be very easy to split to a new repo.
2. flow-client, should investigate to see if the fusion code could be extracted to a different module e.g. fusion-client, so that fusion-client could depend on flow-client, but flow-client shouldn’t depend on fusion-client.
3. flow-server, should investigate to see if the fusion code could be extracted to a different module e.g. fusion-server, so that fusion-server could depend on flow-server, but flow-server shouldn’t depend on fusion-server.
4. flow-maven-plugin -> vaadin-maven-plugin that then uses a SPI architecture to allow Flow and Fusion to add its own hooks into the various phases needed during the build. The same underlying logic would then also be shared with e.g. a Gradle plugin and the dev mode that runs inside the application server.

The investigation is time-boxed to 3 days.

[haijian-vaadin]

let’s close this one now as the research is done, we can reopen it if more research is needed.

[haijian-vaadin]

The research result is available at https://docs.google.com/document/d/1UC-H6J1VmXOdzACWIwenFhP4yOEfjCpMeMiY3UL_Od4/edit#