Generate an Ant build file for the project. Previous archived versions of plugins reference documentations are located here.
There are also some sandbox plugins into our source repository. The Maven Scripting Plugin wraps the Scripting API according to JSR223.Īssists with release staging and promotion.Īllows to share configuration across plugins.ĭownload and unpack the maven wrapper distribution (works only with Maven 4) Publish your Maven website to a scm location. Release the current project - updating the POM and tagging in the SCM.Ĭopy remote resources to the output directory for inclusion in the artifact.Įxecute SCM commands for the current project.
Generate a PDF version of your project's documentation.Ĭreate a Maven plugin descriptor for any mojos found in the source tree, to include in the JAR.
Use the gnu patch tool to apply patch files to source code. Run a set of Maven projects and verify the output.
Get information about the working environment for the project. Generate a skeleton project structure from an archetype.īuild an assembly (distribution) of sources and/or binaries.ĭependency manipulation (copy, unpack) and analysis.Įnvironmental constraint checking (Maven Version, JDK etc), User Custom Rule Execution.Ĭreate signatures for the artifacts and poms. Run a set of ant tasks from a phase of the build. These are miscellaneous tools available through Maven by default. Generate a report based on the results of unit tests. Generate a Linkcheck report of your project's documentation. Generate a Description of a Project (DOAP) file from a POM. Generate a report from an issue tracker or a change document. Generate a list of recent changes from your SCM. Plugins which generate reports, are configured as reports in the POM and run under the site generation lifecycle. Generate an EAR from the current project.īuild an EJB (and optional client) from the current project.īuild a JavaEE application client from the current project.īuild an Uber-JAR from the current project, including dependencies.īuild a source-JAR from the current project. These plugins relate to packaging respective artifact types. Useful for integration tests - verifies the existence of certain conditions. Run the JUnit unit tests in an isolated classloader.
Install the built artifact into the local repository.Ĭopy the resources to the output directory for including in the JAR. Run the JUnit integration tests in an isolated classloader. They may have multiple goals as well.ĭeploy the built artifact to the remote repository. Plugins corresponding to default core phases (ie. (Plugins are organized according to a directory structure that resembles the standard Java package naming convention) Plugin To see the most up-to-date list browse the Maven repository, specifically the org/apache/maven/plugins subfolder. You can read more about the localization of our plugins and how you can help. Because the result of a Reporting plugin is part of the generated site, Reporting plugins should be both internationalized and localized.
There are the build and the reporting plugins: Looking for a specific goal to execute? This page lists the core plugins and others. Maven is - at its heart - a plugin execution framework all work is done by plugins.