Checkstyle, PMD und FindBugs scheinen sich auf den ersten Blick zu ähneln. Alle drei suchen nach bekannten Fehlermustern (Bug Patterns). Da sie aber. Overview. Checkstyle is a development tool to help programmers write Java code that adheres to a coding standard. It automates the process of checking Java. Available Plugins. Maven is - at its heart - a plugin execution framework; all work is done by plugins. Looking for a specific goal to execute? This page lists the. Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-compiler-plugin:2.3.2:testCompile (execution: default-testCompile, phase: test.
Maven – Available Plugins. Maven is - at its heart - a plugin execution framework; all work is done by plugins. Looking for a specific goal to execute?
![Maven Checkstyle Configuration File Maven Checkstyle Configuration File](http://sonar.codehaus.org/wp-content/uploads/2010/03/widget.jpg)
This page lists the core plugins and others. There are the build and the reporting plugins: Supported By The Maven Project. To see the most up- to- date list browse the Maven repository, specifically the org/apache/maven/plugins subfolder. Plugins are organized according to a directory structure that resembles the standard Java package naming convention)Plugin. Type*Version. Release Date. Description. Source Repository. Issue Tracking. Core plugins.
![Maven Checkstyle Configuration File Maven Checkstyle Configuration File](http://static.commentcamarche.net/ccm.net/pictures/KhLUNZB5N0kE4zTKWx68feXzxAF2mfmbzn0aOP5XrJa8D56VwDWz4Vw58xH9YsZd-mav1-s-.png)
Plugins corresponding to default core phases (ie. They may have multiple goals as well. B3. 0. 0. 20. 15- 1.
SonarQube® software (previously called Sonar) is an open source quality management platform, dedicated to continuously analyze and measure technical quality, from. I have to agree that this has gone the opposite way of the Maven manifesto (so to speak). It makes a simple thing so complex that even reading all about it, I can't.
Clean up after the build. SVNJIRAcompiler. B3. Compiles Java sources. SVNJIRAdeploy. B2.
Deploy the built artifact to the remote repository. SVNJIRAfailsafe. B2. Run the JUnit integration tests in an isolated classloader. GITJIRAinstall. B2.
Install the built artifact into the local repository. SVNJIRAresources.
B3. 0. 1. 20. 16- 0. Copy the resources to the output directory for including in the JAR. SVNJIRAsite. B3. 5. Generate a site for the current project. SVNJIRAsurefire. B2. Run the JUnit unit tests in an isolated classloader.
GITJIRAverifier. B1. Useful for integration tests - verifies the existence of certain conditions.
SVNJIRAPackaging types/tools. These plugins relate to packaging respective artifact types. B2. 1. 0. 1. 20. 15- 0. Generate an EAR from the current project. SVNJIRAejb. B2. 5. Build an EJB (and optional client) from the current project.
SVNJIRAjar. B3. 0. Build a JAR from the current project.
SVNJIRArar. B2. 4. Build a RAR from the current project. SVNJIRAwar. B2. 6.
Build a WAR from the current project. SVNJIRAapp- client/acr.
B3. 0. 0. 20. 15- 0. Build a Java. EE application client from the current project. SVNJIRAshade. B2. Build an Uber- JAR from the current project, including dependencies. SVNJIRAsource. B3.
Build a source- JAR from the current project. SVNJIRAReporting plugins. Plugins which generate reports, are configured as reports in the POM and run under the site generation lifecycle.
R2. 3. 20. 14- 0. Generate a list of recent changes from your SCM. SVNJIRAchanges. B+R2. Generate a report from an issue tracker or a change document. SVNJIRAcheckstyle.
B+R2. 1. 72. 01. 5- 1. Generate a Checkstyle report. SVNJIRAdoap. B1. 2. Generate a Description of a Project (DOAP) file from a POM. SVNJIRAdocck. B1. Documentation checker plugin. SVNJIRAjavadoc. B+R2.
Generate Javadoc for the project. SVNJIRAjdeps. B3. Run JDK's JDeps tool on the project. SVNJIRAjxr. R2. 5. Generate a source cross reference.
SVNJIRAlinkcheck. R1. 2. 20. 14- 1. Generate a Linkcheck report of your project's documentation. SVNJIRApmd. B+R3. Generate a PMD report. SVNJIRAproject- info- reports. R2. 9. 20. 16- 0.
Generate standard project reports. SVNJIRAsurefire- report. R2. 1. 9. 1. 20. 16- 0. Generate a report based on the results of unit tests. GITJIRATools. These are miscellaneous tools available through Maven by default. B2. 4. 20. 14- 1.
Generate an Ant build file for the project. SVNJIRAantrun. B1.
Run a set of ant tasks from a phase of the build. SVNJIRAarchetype. B2. 4. 20. 15- 0.
Generate a skeleton project structure from an archetype. GITJIRAassembly. B2. Build an assembly (distribution) of sources and/or binaries.
SVNJIRAdependency. B+R2. 1. 02. 01. 5- 0. Dependency manipulation (copy, unpack) and analysis. SVNJIRAenforcer. B1.
Environmental constraint checking (Maven Version, JDK etc), User Custom Rule Execution. SVNJIRAgpg. B1. 6. Create signatures for the artifacts and poms. SVNJIRAhelp. B2. 2. Get information about the working environment for the project. SVNJIRAinvoker. B+R2. Run a set of Maven projects and verify the output.
SVNJIRAjarsigner. B1. 4. 20. 15- 0. Signs or verifies project artifacts. SVNJIRApatch. B1. Use the gnu patch tool to apply patch files to source code. SVNJIRApdf. B1. 3.
Generate a PDF version of your project's documentation. SVNJIRAplugin. B+R3. Create a Maven plugin descriptor for any mojos found in the source tree, to include in the JAR.
SVNJIRArelease. B2. Release the current project - updating the POM and tagging in the SCM. SVNJIRAremote- resources. B1. 5. 20. 13- 0. Copy remote resources to the output directory for inclusion in the artifact. SVNJIRArepository.
B2. 4. 20. 15- 0. Plugin to help with repository- based tasks. SVNJIRAscm. B1. 9. Execute SCM commands for the current project. GITJIRAscm- publish.
B1. 1. 20. 14- 0. Publish your Maven website to a scm location.
SVNJIRAstage. B1. Assists with release staging and promotion. SVNJIRAtoolchains. B1. 1. 20. 14- 1. Allows to share configuration across plugins. SVNJIRA* Build or Reporting plugin. There are also some sandbox plugins into our source repository.
Previous archived versions of plugins reference documentations are located here.