MVN integration

Please fix maven dependency issue I have reported long ago, when module A references a_v1, b_v1 and Module B references  a_v1, b_v2 while A has dependency on B the IntelliJ project class is a_v1, b_v1, b_v2 in random order this is wrong since maven final class path via dependency:tree for module A would be a_v1, b_v1. This makes impossible to work on the big projects where every team has it is own dependency management.

Please allow an option to designate a particular maven project as the main one and have Idea to build the project class path the same as mvn dependency:tree for that particular maven module would produce.

Currently IntelliJ builds project class path as union of all the modules dependencies (so multiple versions collide) in the project which not always useful


Please sign in to leave a comment.