You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dan Fabulich (JIRA)" <ji...@codehaus.org> on 2008/02/05 00:48:57 UTC
[jira] Created: (MPH-34) Add a new help goal that describes the
current lifecycle bindings
Add a new help goal that describes the current lifecycle bindings
-----------------------------------------------------------------
Key: MPH-34
URL: http://jira.codehaus.org/browse/MPH-34
Project: Maven 2.x Help Plugin
Issue Type: New Feature
Reporter: Dan Fabulich
There should be a goal that examines the current POM's lifecycle and prints out a list of phases and lifecycle bindings. In full mode it should print out a list of every phase regardless of whether it has a lifecycle binding; in medium/default mode it should just print out phases that have bindings. It could look something like this:
* process-resources
resources:resources
* compile
compiler:compile
* process-test-resources
resources:testResource
* test-compile
compiler:testCompile
mygroup:myartifact:1.0.1:foo
* test
surefire:test
* package
jar:jar
* install
install:install
* deploy
deploy:deploy
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MPH-34) Add a new help goal that describes the
current lifecycle bindings
Posted by "Vincent Siveton (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPH-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vincent Siveton closed MPH-34.
------------------------------
Resolution: Fixed
MPH-30 should do it for you
{noformat}
# mvn help:describe -Dcmd=compile
...
[INFO] 'compile' is a phase corresponding to this plugin:
org.apache.maven.plugins:maven-compiler-plugin:compile
It is a part of the lifecycle for the POM packaging 'maven-plugin'. This lifecycle includes the
following phases:
* validate: NOT DEFINED
* initialize: NOT DEFINED
* generate-sources: NOT DEFINED
* process-sources: NOT DEFINED
* generate-resources: org.apache.maven.plugins:maven-plugin-plugin:descriptor
* process-resources: org.apache.maven.plugins:maven-resources-plugin:resources
* compile: org.apache.maven.plugins:maven-compiler-plugin:compile
* process-classes: NOT DEFINED
* generate-test-sources: NOT DEFINED
* process-test-sources: NOT DEFINED
* generate-test-resources: NOT DEFINED
* process-test-resources: org.apache.maven.plugins:maven-resources-plugin:testResources
* test-compile: org.apache.maven.plugins:maven-compiler-plugin:testCompile
* process-test-classes: NOT DEFINED
* test: org.apache.maven.plugins:maven-surefire-plugin:test
* package: org.apache.maven.plugins:maven-jar-plugin:jar, org.apache.maven.plugins:maven-plugin
-plugin:addPluginArtifactMetadata
* pre-integration-test: NOT DEFINED
* integration-test: NOT DEFINED
* post-integration-test: NOT DEFINED
* verify: NOT DEFINED
* install: org.apache.maven.plugins:maven-install-plugin:install, org.apache.maven.plugins:mave
n-plugin-plugin:updateRegistry
* deploy: org.apache.maven.plugins:maven-deploy-plugin:deploy
{noformat}
> Add a new help goal that describes the current lifecycle bindings
> -----------------------------------------------------------------
>
> Key: MPH-34
> URL: http://jira.codehaus.org/browse/MPH-34
> Project: Maven 2.x Help Plugin
> Issue Type: New Feature
> Reporter: Dan Fabulich
>
> There should be a goal that examines the current POM's lifecycle and prints out a list of phases and lifecycle bindings. In full mode it should print out a list of every phase regardless of whether it has a lifecycle binding; in medium/default mode it should just print out phases that have bindings. It could look something like this:
> {noformat}
> * process-resources
> resources:resources
> * compile
> compiler:compile
> * process-test-resources
> resources:testResource
> * test-compile
> compiler:testCompile
> mygroup:myartifact:1.0.1:foo
> * test
> surefire:test
> * package
> jar:jar
> * install
> install:install
> * deploy
> deploy:deploy
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MPH-34) Add a new help goal that describes the
current lifecycle bindings
Posted by "Dan Fabulich (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPH-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122350 ]
Dan Fabulich commented on MPH-34:
---------------------------------
Even better would be for full mode to include the first sentence of the description of every mojo on the list, just like Javadoc.
> Add a new help goal that describes the current lifecycle bindings
> -----------------------------------------------------------------
>
> Key: MPH-34
> URL: http://jira.codehaus.org/browse/MPH-34
> Project: Maven 2.x Help Plugin
> Issue Type: New Feature
> Reporter: Dan Fabulich
>
> There should be a goal that examines the current POM's lifecycle and prints out a list of phases and lifecycle bindings. In full mode it should print out a list of every phase regardless of whether it has a lifecycle binding; in medium/default mode it should just print out phases that have bindings. It could look something like this:
> {noformat}
> * process-resources
> resources:resources
> * compile
> compiler:compile
> * process-test-resources
> resources:testResource
> * test-compile
> compiler:testCompile
> mygroup:myartifact:1.0.1:foo
> * test
> surefire:test
> * package
> jar:jar
> * install
> install:install
> * deploy
> deploy:deploy
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MPH-34) Add a new help goal that describes the
current lifecycle bindings
Posted by "Dan Fabulich (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MPH-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Fabulich updated MPH-34:
----------------------------
Description:
There should be a goal that examines the current POM's lifecycle and prints out a list of phases and lifecycle bindings. In full mode it should print out a list of every phase regardless of whether it has a lifecycle binding; in medium/default mode it should just print out phases that have bindings. It could look something like this:
{noformat}
* process-resources
resources:resources
* compile
compiler:compile
* process-test-resources
resources:testResource
* test-compile
compiler:testCompile
mygroup:myartifact:1.0.1:foo
* test
surefire:test
* package
jar:jar
* install
install:install
* deploy
deploy:deploy
{noformat}
was:
There should be a goal that examines the current POM's lifecycle and prints out a list of phases and lifecycle bindings. In full mode it should print out a list of every phase regardless of whether it has a lifecycle binding; in medium/default mode it should just print out phases that have bindings. It could look something like this:
* process-resources
resources:resources
* compile
compiler:compile
* process-test-resources
resources:testResource
* test-compile
compiler:testCompile
mygroup:myartifact:1.0.1:foo
* test
surefire:test
* package
jar:jar
* install
install:install
* deploy
deploy:deploy
> Add a new help goal that describes the current lifecycle bindings
> -----------------------------------------------------------------
>
> Key: MPH-34
> URL: http://jira.codehaus.org/browse/MPH-34
> Project: Maven 2.x Help Plugin
> Issue Type: New Feature
> Reporter: Dan Fabulich
>
> There should be a goal that examines the current POM's lifecycle and prints out a list of phases and lifecycle bindings. In full mode it should print out a list of every phase regardless of whether it has a lifecycle binding; in medium/default mode it should just print out phases that have bindings. It could look something like this:
> {noformat}
> * process-resources
> resources:resources
> * compile
> compiler:compile
> * process-test-resources
> resources:testResource
> * test-compile
> compiler:testCompile
> mygroup:myartifact:1.0.1:foo
> * test
> surefire:test
> * package
> jar:jar
> * install
> install:install
> * deploy
> deploy:deploy
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira