Start from m2e 0.13.0 (if not earlier than), you can convert a Java project to Maven project from the context menu. Here is how: Right click the Java project to pop up the context menu Select Configure > Convert to Maven Project Here is the detailed steps with screen shots.
I want the jar to be in a 3rdparty lib in source control, and link to it by relative path from the pom.xml file. If you really want this (understand, if you can’t use a corporate repository), then my advice would be to use a “file repository” local to the project and to not use … Read more
If you want to skip running and compiling tests: mvn -Dmaven.test.skip=true install If you want to compile but not run tests: mvn install -DskipTests
Resolved by adding the following exclusion in the dependencies (of pom.xml) that caused conflict. <exclusions> <exclusion> <groupId>org.slf4j</groupId> <artifactId>slf4j-log4j12</artifactId> </exclusion> </exclusions>
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>
Try the maven-exec-plugin. From there: mvn exec:java -Dexec.mainClass=”com.example.Main” This will run your class in the JVM. You can use -Dexec.args=”arg0 arg1″ to pass arguments. If you’re on Windows, apply quotes for exec.mainClass and exec.args: mvn exec:java -D”exec.mainClass”=”com.example.Main” If you’re doing this regularly, you can add the parameters into the pom.xml as well: <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>exec-maven-plugin</artifactId> … Read more
From the Maven Embedder documentation: -fae,–fail-at-end Only fail the build afterwards; allow all non-impacted builds to continue -fn,–fail-never NEVER fail the build, regardless of project result So if you are testing one module than you are safe using -fae. Otherwise, if you have multiple modules, and if you want all of them tested (even the … Read more
In my opinion, to answer this question, you need to think in terms of project life cycle and version control. In other words, does the parent pom have its own life cycle i.e. can it be released separately of the other modules or not? If the answer is yes (and this is the case of … Read more
How do I find a repository (if any) that contains this artifact? Unfortunately due the binary license there is no public repository with the Oracle Driver JAR. This happens with many dependencies but is not Maven’s fault. If you happen to find a public repository containing the JAR you can be sure that is illegal. … Read more
The Maven Dependency Plugin will help, especially the dependency:analyze goal: dependency:analyze analyzes the dependencies of this project and determines which are: used and declared; used and undeclared; unused and declared. Another thing that might help to do some cleanup is the Dependency Convergence report from the Maven Project Info Reports Plugin.