The <scope> element can take 6 values: compile, provided, runtime, test, system and import. This scope is used to limit the transitivity of a dependency, and also to affect the classpath used for various build tasks. compile This is the default scope, used if none is specified. Compile dependencies are available in all classpaths of … Read more
maven-compiler-plugin it’s already present in plugins hierarchy dependency in pom.xml. Check in Effective POM. For short you can use properties like this: <properties> <maven.compiler.source>1.8</maven.compiler.source> <maven.compiler.target>1.8</maven.compiler.target> </properties> I’m using Maven 3.2.5.
You still need to add <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-dependency-plugin</artifactId> </plugin> </plugins> in your build, because pluginManagement is only a way to share the same plugin configuration across all your project modules. From Maven documentation: pluginManagement: is an element that is seen along side plugins. Plugin Management contains plugin elements in much the same way, except … Read more
Right-click on the module, select “Add framework support…”, and check the “Maven” technology. (This also creates a pom.xml for you to modify.) If you mean adding source repository elements, I think you need to do that manually–not sure. Pre-IntelliJ 13 this won’t convert the project to the Maven Standard Directory Layout, 13+ it will.
I’m fashionably late to this question, but I think it’s worth a clearer response than the accepted one (which is correct, but doesn’t emphasize the actual important part, which you need to deduce yourself). In the parent POM, the main difference between the <dependencies> and <dependencyManagement> is this: Artifacts specified in the <dependencies> section will … Read more