3) Analyze and properly associate dependencies. There are a number of very outdated dependency references which should be updated (e.g. gridgain-commons-deps > commons-logging > 1.1.1 - released 11/2007). Furthermore, the root pom specifies a number of dependencies which i don't believe are truly common across all modules. For example i believe a number of the scala related dependencies can safely be moved from the root to gridgain-scalar, etc.
Can we make a few improvements to use of Maven...
1) Make full use of all appropriate build phases in the maven lifecycle and therefore remove dependency on ant build (see https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#Setting_Up_Your_Project_to_Use_the_Build_Lifecycle)
2) Move all modules to the Maven standard directory layout (see https://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html)
3) Analyze and properly associate dependencies. There are a number of very outdated dependency references which should be updated (e.g. gridgain-commons-deps > commons-logging > 1.1.1 - released 11/2007). Furthermore, the root pom specifies a number of dependencies which i don't believe are truly common across all modules. For example i believe a number of the scala related dependencies can safely be moved from the root to gridgain-scalar, etc.
4) Can we specify source and javadoc artifacts such that maven users can download these when downloading our main distribution (see https://maven.apache.org/plugin-developers/cookbook/attach-source-javadoc-artifacts.html)