Check how your maven-compiler-plugin is configured, it should use java version 7 or higher: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <version>3.1</version> <configuration> <source>1.7</source> <target>1.7</target> </configuration> </plugin> For a more complete answer see the one below.
You can do this with the Versions Maven Plugin. Check the following goals: versions:display-dependency-updates scans a project’s dependencies and produces a report of those dependencies which have newer versions available. versions:display-plugin-updates scans a project’s plugins and produces a report of those plugins which have newer versions available. Here is a sample output (taken from the … Read more
I wouldn’t expect too much from Maven 3. The people behind the Maven pedigree of build tools have always held the assumption that project builds are homogeneous, that is: all build problems fundamentally boil down to the same problem. This view of the world can be held fairly consistently in the face of opposing views … Read more
Found this page today. Maven CLI Options Reference. Text version to make it easy to copy/paste Maven CLI Options Reference Options >> Description -am,–also-make >> If project list is specified, also build projects required by the list -amd,–also-make-dependents >> If project list is specified, also build projects that depend on projects on the list -B,–batch-mode … Read more
<project> <groupId>org.koshik.javabrains</groupId> <artifactId>JarName</artifactId> (A fldernamed JarName was created) <version>1.0-SNAPSHOT</version> <packaging>jar</packaging> <name>JarName</name> <url>http://maven.apache.org</url> <properties> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> </properties> <build> <plugins> <plugin> <groupId>org.jibx</groupId> <artifactId>jibx-maven-plugin</artifactId> <version>1.2.4</version> <executions> <execution> <goals> <goal>bind</goal> </goals> </execution> </executions> </plugin> </plugins> </build> <dependencies> <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>3.8.1</version> <scope>test</scope> </dependency> </dependencies> </project> You can also place plugins in the <build> section of <profile> if you use maven … Read more
Using the same plugin, you can generate javadoc in a folder using mvn javadoc:javadoc It puts the help content under target/site/apidocs You can change the output folder by using the plugin configuration parameter reportOutputDirectory Please refer to: Apache Maven Javadoc Plugin
I was facing the same error and fixed it like that: Open settings by pressing Ctrl+Alt+S and navigate to Build, Execution, Deployment | Build Tools | Maven | Importing Check JDK for Importer and change the exact version of JDK (example : 1.8.0.250) installed on your machine from the drop-down. After doing the same it … Read more
You should add the maven-jxr-plugin to the reportingPlugin section. <reporting> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-jxr-plugin</artifactId> <version>3.3.0</version> </plugin> </plugins> </reporting> Re run it and enjoy. BTW, maybe you’ll need to run once the jxr:jxr goal to first generate some file that will be used by pmd.
If the file is placed under target/classes after compiling, then it is already in a directory that is part of the build path. The directory src/main/resources is the Maven default directory for such resources, and it is automatically placed to the build path by the Eclipse Maven plugin (M2E). So, there is no need to … Read more
I recommend the following presentation that discusses the practical realities of doing continuous delivery with Maven: You tube presentation on CD with Maven Slides The key takeaway is each build is a potential release, so don’t use snapshots.