You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/12/18 04:22:19 UTC

[jira] Updated: (MNG-3779) Improve error message when trying to execute moojo with no pom.xml

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

Brett Porter updated MNG-3779:
------------------------------

    Fix Version/s: 2.0.11

> Improve error message when trying to execute moojo with no pom.xml
> ------------------------------------------------------------------
>
>                 Key: MNG-3779
>                 URL: http://jira.codehaus.org/browse/MNG-3779
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Errors, Logging
>    Affects Versions: 2.0.9, 2.1.0-M1
>            Reporter: Samuel Le Berrigaud
>             Fix For: 2.0.11
>
>
> I've seen many users on the mailing lists or in my company who get this error message:
> bq. Cannot execute mojo: resources. It requires a project with an existing pom.xml, but the build is not using one.
> Most often than not they do not understand what the cause of the problem is.
> Most often that not this is simply because they are 1 directory up or down relatively to the directory that contains the pom.xml of the project they want to build.
> I suggest that the error message should be updated to something like:
> bq. Cannot execute mojo "bla". Maven was executed in directory "foo" and it doesn't contain a {{pom.xml}}
> Moreover, maven should look 1 directory up and 1 directory down from the {{basedir}} for {{pom.xml}} files. And if one is detected suggest the user to move to that directory.

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