This is the default scope, used if none is specified. Compile dependencies are available in all classpaths of a project. Furthermore, those dependencies are propagated to dependent projects. (From Maven documentation: https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope)

This is much like compile, but indicates you expect the JDK or a container to provide the dependency at runtime. This scope is only available on the compilation and test classpath, and is not transitive. (From Maven documentation: https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope)

This scope indicates that the dependency is not required for compilation, but is for execution. It is in the runtime and test classpaths, but not the compile classpath. (From Maven documentation: https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope)

This scope is similar to provided except that you have to provide the JAR which contains it explicitly. The artifact is always available and is not looked up in a repository. (From Maven documentation: https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope)

This scope indicates that the dependency is not required for normal use of the application, and is only available for the test compilation and execution phases. This scope is not transitive. (From Maven documentation: https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope)