Many a times when you need to understand or optimize the dependency tree in Eclipse projects, it’s simpler to look at .classpath file or at the build path of Eclipse project. However it doesn’t remain practical for a big workspace as .classpath file contains many other things other than <classpathentry/> tags and also you have to open individual .classpath files in different Eclipse projects. Looking at Eclipse buildpath becomes too repetitive and mechanical in a big workspace.
eclipse-to-maven project supports the functionality to print the Eclipse dependency tree in readable format. The steps on how to use this it are mentioned in the README of the project.
Leave a Reply