You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2009/04/24 21:27:44 UTC

[jira] Closed: (MNG-4054) Command Line interprets bogus options

     [ http://jira.codehaus.org/browse/MNG-4054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Casey closed MNG-4054.
---------------------------

      Assignee: John Casey
    Resolution: Cannot Reproduce

I've tried this with Maven 2.1.0, 2.0.10, and 2.1.1-SNAPSHOT, and I cannot reproduce this error. I get:

{noformat}
Betelgeuse:maven-2.1.x jdcasey$ mvn -XOXOXOXOXOXOX clean 
Loading Maven environment from: '/Users/jdcasey/workspace/Open Source Projects/maven/maven-2.1.x/MAVEN_ENV'
JDK 1.5
2.1.0
No MAVEN_OPTS specified.
--> Command was: /Users/jdcasey/apps/maven/apache-maven-2.1.0/bin/mvn  -XOXOXOXOXOXOX clean
+ Error stacktraces are turned on.
Apache Maven 2.1.0 (r755702; 2009-03-18 15:10:27-0400)
Java version: 1.5.0_16

...


[INFO] Invalid task 'OXOXOXOXOXOX': you must specify a valid lifecycle phase, or a goal in the format plugin:goal or pluginGroupId:pluginArtifactId:pluginVersion:goal
[INFO] ------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.BuildFailureException: Invalid task 'OXOXOXOXOXOX': you must specify a valid lifecycle phase, or a goal in the format plugin:goal or pluginGroupId:pluginArtifactId:pluginVersion:goal
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1765)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:446)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:176)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
        at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
{noformat}

> Command Line interprets bogus options
> -------------------------------------
>
>                 Key: MNG-4054
>                 URL: http://jira.codehaus.org/browse/MNG-4054
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Command Line
>    Affects Versions: 2.0.10, 2.1.0-M1, 3.0-alpha-1, 3.0-alpha-2
>            Reporter: Paul Benedict
>            Assignee: John Casey
>            Priority: Minor
>             Fix For: 2.1.1
>
>
> The command line interpreter obviously only matches against the starting portion of a known option. 
> To execute offline, this is acceptable: mvn -outside
> To execute in debug mode, this is acceptable mvn -XOXOXOXOXOX
> You can do this with any option. Get the first couple letters right and you'll trigger perhaps an unintended option.

-- 
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