[ http://jira.codehaus.org/browse/MNG-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126971 ]
barend edited comment on MNG-3368 at 3/12/08 10:40 AM: ------------------------------------------------------------- The Java VM itself provides the following options: -version -----> print product version and exit -version:<value> -----> require the specified version to run -showversion -----> print product version and continue Consider providing the same options in Maven. (comment edited: apparently Confluence table syntax isn't supported) was (Author: barend): The Java VM itself provides the following options: | {{-version}} | print product version and exit | | {{-version:<value>}} | require the specified version to run | | {{-showversion}} | print product version and continue | Consider providing the same options in Maven. > Printing version (-v argument) should not stop lifecycle execution > ------------------------------------------------------------------ > > Key: MNG-3368 > URL: http://jira.codehaus.org/browse/MNG-3368 > Project: Maven 2 > Issue Type: Bug > Components: Bootstrap & Build, Command Line > Affects Versions: 2.0.8 > Reporter: Paul Benedict > Fix For: 2.0.10 > > > I wanted to always print the Maven version when I build, but unfortunately > Maven immediately quits after outputting the version. This option should not > quit when a lifecycle is also specified. Example: mvn -v install -- 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