Hi
First topic: git repository structure.
1. Single repository
2. Multiple repositories
First of all I must admit that if we are talkin for our internal developing we are ok with both solution.
But since project grows and we involving more and more peoples some issue with multiple repositories become harder and harder.
For example:
1. It's much easier to explain for new contributor how to build and run product from any tag or snapshot
when it is in one repository than in multiple.
2. Since we releasing very frequently we are releasing everything even if some plugin has no changes at all.
3. When we develop some big feature which require changes in several project, bulding, testing and contribution
become to not trivial task.
In the same time we are rejecting multiple repository approach.
The basic idea is to hold minimal starting version (SDK and everything related to it) in one repository.
Everything else will be in separate repositories grouped by feature with individual (not depending to SDK) lifecycle.
About maven groupID.
@Dmitry can you confirm that we MUST use org.eclipse.che as groupID? Can it be something like this org.eclipse.che.plugin for some cases?
Sergii Kabashniuk