I think you misunderstood Roman. He talk only about his part of the job - release.
But for me and for Vitaly as for developer, multi-repository approach in current state,
without new process technologies like BOM gives more disadvantaged than advantages.
We always rebuild, re-release, facing with long merging problem etc. The easiest way to solve it, is to put all repositories at one.
But we see the final idea that you are trying to tell us.
As compromise variant for initial contribution, which in future will allow as to use BOM and not release unchanged plugins, we propose 3d version of structure with 3 git repositories
1. che-core - everything need to build plugins.
----
maven-parent-pom
maven-depmgt-pom
commons
platform-api
platform-api-client-gwt
ide
vfs-impl
test-framework
.....
2. che-plugins - all
plugin-java
plugin-editor-codemirror
plugin-editor-orion
plugin-php
plugin-git
plugin-datasource
plugin-angularjs
plugin-bower
plugin-gulp
plugin-grunt
plugin-npm
plugin-yeoman
plugin-cpp
plugin-ruby
plugin-go
plugin-python
plugin-tour
plugin-sdk
plugin-runner
3. che-assembly-sdk
Eventually after 1 before 2 we will have che-boms.
And all plugins will be able to use it. When we can work on the improvements with plugin building and running without rebuild-all. After that we can separate che-plugins into individual repositories.
WDYT?