with below command you can see all the dependency in the command prompt
projectpath$ mvn dependency:tree
Project Dependencies briefly introduced three of the five dependency scopes:
provided. Scope controls which dependencies are available in which classpath, and which dependencies are included with an application. Let’s explore each scope in detail:
- compile+ is the default scope; all dependencies are
compile-scoped if a scope is not supplied.
compiledependencies are available in all classpaths, and they are packaged.
- provided+ dependencies are used when you expect the JDK or a container to provide them. For example, if you were developing a web application, you would need the Servlet API available on the compile classpath to compile a servlet, but you wouldn’t want to include the Servlet API in the packaged WAR; the Servlet API JAR is supplied by your application server or servlet container.
provideddependencies are available on the compilation classpath (not runtime). They are not transitive, nor are they packaged.
- runtime+ dependencies are required to execute and test the system, but they are not required for compilation. For example, you may need a JDBC API JAR at compile time and the JDBC driver implementation only at runtime.
- test+-scoped dependencies are not required during the normal operation of an application, and they are available only during test compilation and execution phases.
systemscope is similar to
providedexcept that you have to provide an explicit path to the JAR on the local file system. This is intended to allow compilation against native objects that may be part of the system libraries. The artifact is assumed to always be available and is not looked up in a repository. If you declare the scope to be
system, you must also provide the
systemPathelement. Note that this scope is not recommended (you should always try to reference dependencies in a public or custom Maven repository).