java - How can you display the Maven dependency tree for the *plugins* in your project?

ID : 27608

viewed : 85

Tags : javapluginsmavenjava

Top 5 Answer for java - How can you display the Maven dependency tree for the *plugins* in your project?

vote vote


The output via mvn -X will printout the information indirectly. Currently there is no other option to get the dependencies of a Maven-Plugin.

Update You can use the following command to get a list of plugin dependencies (resolve-plugin goal from dependencies plugin):

mvn org.apache.maven.plugins:maven-dependency-plugin:2.10:resolve-plugins 

The shorter version is (and it is a bad habit to specify plugin versions)

mvn dependency:resolve-plugins 
vote vote


If you are using any IDE like IDEA IntelliJ or Eclipse:

  • You can add this below plugin in your pom.xml
  • Once done, On the Maven window (on the right of IDE), you will find a new plugin called as Dependencies
  • Expand that and you will see the dependency:tree goal, double click on it and run it, you should see the full dependency tree

Plugin to be added in POM:

<build>     <plugins>         <plugin>             <artifactId>maven-dependency-plugin</artifactId>             <configuration>                 <source>1.8</source>                 <target>1.8</target>             </configuration>         </plugin>     </plugins> </build> 
vote vote


vote vote


I've been working with brackets-shell for some time now, here are some of my findings:

  • brackets-shell is primarily developed as a shell under the brackets IDE project, but the project can run any web application. You just need to point it to your own html page. Clint Berry wrote an excellent tutorial about doing just this:
  • The project is backed by Adobe and has a lot of activity
  • Documentation could be better

  • platform support They support Windows, Mac and Linux. An installer package can also be created. I only tested it on Win and Mac, it works great.

  • feature support html5, css3, js. Html5 video does not work out of the box, but is very easy to enable (by default the ffmpegsumo.dll is not copied into the installer, if you change the script to copy it it will work).
  • native features menu bar, 'open file with', file system access. I am not using any of these, as all I need is the communication with the node process.
  • extensibility a nodejs is built in, and you can communicate with node from your web application. In this way, you can use node to access the filesystem etc.
  • architecture The project is well set up, keeping a nice separation between the shell project and your own web app running inside it. In your own application, a global appshell object is available which gives you access to the brackets functionality (filesystem access, communication with node process, ...).
vote vote


One thing to note (if you care), is that the Electron officially does not support Windows Vista. Vista's market share is about halfway between OSX 10.9 and 10.10 (both of which are fully supported by Electron). Vista is also still supported by Microsoft until 2017.

NW.js works fine in Vista, as well as OSX 10.9+. NW.js works on Ubuntu, Debian, Zorin, Manjaro, Arch, and most other Debian based Linux OS's. Electron has refused PR's to fix Ubuntu specific bugs on their platform which is concerning.

NW.js works in XP too. Currently 18% of the market is still on XP. So if you're desktop application is more general purpose or wants to have access to the late adopters still on XP, you're probably better off with NW.js (0.14.7) as Electron only supports Win 7 and up.

If you use NW.js 0.12.3 you can also support OSX 10.6+ and very old versions of Debian based Linux OS's like Ubuntu, and Win XP+. It is recommended that you do special builds just for those legacy systems though and use the newer versions of NW.js for newer OS's.

Top 3 video Explaining java - How can you display the Maven dependency tree for the *plugins* in your project?