The role of dependency type dependency type in Maven

Look at the following POM configuration

...<dependency> <groupId>xxx</groupId> <artifactId>yyy</artifactId> <TYPE>EJB </type></dependency>, .....

This <type> many MAVEN-related materials have not been mentioned, and the Internet search for Chinese resources, these articles are compile, runtime, test and so on is the concept of the scope of "dependency type" <type> concept. Moreover, there are very few explanations for this <type>.

I also looked at Maven 3 cookbook after finding some words, anti-launch type of the role.

Read the original text (P134. How it works ... ）：

Adding the type of apk to the dependency allows the Maven Android plugin to find the Android package of the application.

It's not hard to see,<type>apk</type> telling Maven to use Maven Android plugin to handle <type> for apk dependencies. The presumption <type>ejb</type> is to tell Maven to work with Maven EJB plugin. If you want to know how EJB plugin handles this type of dependency, check out the detailed description of the EJB plugin, which is a lot of information on the plugin.

This article is from the "Bitterjava" blog, make sure to keep this source http://rickqin.blog.51cto.com/1096449/1738774

The role of dependency type dependency type in Maven