プラグインのゴールとその説明を見るには
提供: tknotebook
メインページ>コンピュータの部屋#Java>Maven Tips
特定のプラグインのすべてのゴールとその説明を見たいときは
以下のゴールを実行します。
mvn help:describe -Dplugin=プラグインのGroupdId:ArtifactId
例
mvn help:describe -Dplugin=org.mortbay.jetty:maven-jetty-plugin Name: Maven Jetty Plugin Description: Parent pom for Jetty at Codehaus Group Id: org.mortbay.jetty Artifact Id: maven-jetty-plugin Version: 6.1.26 Goal Prefix: jetty This plugin has 5 goals: jetty:deploy-war Description: This goal is used to run Jetty with a pre-assembled war. It accepts exactly the same options as the run-war goal. However, it doesn't assume that the current artifact is a webapp and doesn't try to assemble it into a war before its execution. So using it makes sense only when used in conjunction with the webApp configuration parameter pointing to a pre-built WAR. This goal is useful e.g. for launching a web app in Jetty as a target for unit-tested HTTP client components. jetty:run Description: This goal is used in-situ on a Maven project without first requiring that the project is assembled into a war, saving time during the development cycle. The plugin forks a parallel lifecycle to ensure that the 'compile' phase has been completed before invoking Jetty. This means that you do not need to explicity execute a 'mvn compile' first. It also means that a 'mvn clean jetty:run' will ensure that a full fresh compile is done before invoking Jetty. Once invoked, the plugin can be configured to run continuously, scanning for changes in the project and automatically performing a hot redeploy when necessary. This allows the developer to concentrate on coding changes to the project using their IDE of choice and have those changes immediately and transparently reflected in the running web container, eliminating development time that is wasted on rebuilding, reassembling and redeploying. You may also specify the location of a jetty.xml file whose contents will be applied before any plugin configuration. This can be used, for example, to deploy a static webapp that is not part of your maven build. There is a reference guide to the configuration parameters for this plugin, and more detailed information with examples in the Configuration Guide. jetty:run-exploded Description: This goal is used to assemble your webapp into an exploded war and automatically deploy it to Jetty. Once invoked, the plugin can be configured to run continuously, scanning for changes in the pom.xml and to WEB-INF/web.xml, WEB-INF/classes or WEB-INF/lib and hot redeploy when a change is detected. You may also specify the location of a jetty.xml file whose contents will be applied before any plugin configuration. This can be used, for example, to deploy a static webapp that is not part of your maven build. There is a reference guide to the configuration parameters for this plugin, and more detailed information with examples in the Configuration Guide. jetty:run-war Description: This goal is used to assemble your webapp into a war and automatically deploy it to Jetty. Once invoked, the plugin can be configured to run continuously, scanning for changes in the project and to the war file and automatically performing a hot redeploy when necessary. You may also specify the location of a jetty.xml file whose contents will be applied before any plugin configuration. This can be used, for example, to deploy a static webapp that is not part of your maven build. There is a reference guide to the configuration parameters for this plugin, and more detailed information with examples in the Configuration Guide. jetty:stop Description: JettyStopMojo - stops a running instance of jetty. The ff are required: -DstopKey=someKey -DstopPort=somePort For more information, run 'mvn help:describe [...] -Ddetail'