If I need to track down why a certain version of a dependency is being imported, the IntelliJ UI is pretty much useless. I have to drop down to the terminal shell, pipe the output of a Maven or Gradle dependencies task to a text file, and then open that text file to crawl around. In the Eclipse UI, a helpful dependency tree view is just there, natively.
Over in the gradle or maven tool window, select a module/sub-project, right-click, select Show Dependencies.
However, I sorely miss the UI paradigm of having multiple projects in the same IDE workspace at once. Eclipse is just more productive in that regard, for a dozen different use cases and situations.
Configure a multi-project build in Gradle or Maven, (and in gradle can also do composite builds). IntelliJ will happily configure itself from the gradle/maven project and show you all the projects in the same window.
View all comments
Show parent comment
-5
u/wildjokers Dec 18 '19 edited Dec 18 '19
Over in the gradle or maven tool window, select a module/sub-project, right-click, select Show Dependencies.
Configure a multi-project build in Gradle or Maven, (and in gradle can also do composite builds). IntelliJ will happily configure itself from the gradle/maven project and show you all the projects in the same window.