By default, Maven doesn’t bundle dependencies in the JAR file it builds, and you’re not providing them on the classpath when you’re trying to execute your JAR file at the command-line. This is why the Java VM can’t find the library class files when trying to execute your code. You could manually specify the libraries … Read more
How to specify the JDK version? Use any of three ways: (1) Spring Boot feature, or use Maven compiler plugin with either (2) source & target or (3) with release. Spring Boot <java.version> is not referenced in the Maven documentation. It is a Spring Boot specificity. It allows to set the source and the target … Read more
IntelliJ should download and add all your dependencies to the project’s classpath automatically as long as your POM is compliant and all the dependencies are available. When importing Maven projects into IntelliJ an information box usually comes up asking you if you want to configure Auto-Import for Maven projects. That means that if you make … Read more
This works for me: <project> … <profiles> <profile> <id>qa</id> <build> <plugins> <plugin> <artifactId>maven-dependency-plugin</artifactId> <executions> <execution> <phase>install</phase> <goals> <goal>copy-dependencies</goal> </goals> <configuration> <outputDirectory>${project.build.directory}/lib</outputDirectory> </configuration> </execution> </executions> </plugin> </plugins> </build> </profile> </profiles> </project>
A Maven lifecycle is an (abstract) concept that covers all steps (or better: all the steps the Maven designers decided to support) that are expected to occur in a project’s development lifetime. These steps (or stages) are called phases in Maven terminology. A Maven plugin is a container for/supplier of goals. Code implemented in goals … Read more