[che-dev] Bug 460944 - Dependency convergence

[Sergii Kabashniuk <skabashnyuk@xxxxxxxxxxx>]

This time I want to discuss with you one of the requirements of enterprise and good sense is dependency convergence. In simple words: all dependencies and transitive dependencies should have same predictable version.

You can read more here 

http://cupofjava.de/blog/2013/02/01/fight-dependency-hell-in-maven/

http://java.dzone.com/articles/dependency-convergence-maven

http://maven.apache.org/enforcer/enforcer-rules/dependencyConvergence.html

To achive this goal I've added a maven  profile  dependency-convergence so you can test that you project is satisfy to this requirement.

Example:

 mvn clean install -Pdependency-convergence

Also we want to introduce a couple of requiroment for all subprojects related to codenvy and che.

1. All dependencies in subproject have to be declared from version taken from 

https://github.com/codenvy/maven-depmgt-pom

2. You should not declare dependencies version in subproject parent pom.

3. All subprojects should pass tests with  dependency-convergence maven profile

4. All plugin should not have version in subprojects and should take it from https://github.com/codenvy/maven-parent-pom

5. Subprojects should try to avoid usage of apache commons and use guava instead.

6.  After project  successfuly pass dependency-convergence maven profile it have to be enabled on jenkins.

A list of project that already pass  dependency-convergence maven profile you can find here https://bugs.eclipse.org/bugs/show_bug.cgi?id=460944.

Plz consider to fix 1-6 requirements as soon as you can.

Sergii Kabashniuk