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 2010/01/12 18:02:55 UTC
[jira] Updated: (MNG-3168) Correct error message when project
descriptor not found
[ http://jira.codehaus.org/browse/MNG-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3168:
------------------------------
Fix Version/s: (was: 2.2.x)
3.0-alpha-7
still a problem in 3.0-alpha-6
> Correct error message when project descriptor not found
> -------------------------------------------------------
>
> Key: MNG-3168
> URL: http://jira.codehaus.org/browse/MNG-3168
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Bootstrap & Build
> Reporter: Chris Eldredge
> Fix For: 3.0-alpha-7
>
>
> When using the "-f" switch and passing the name of a file which does not exist, Maven complains about pom.xml, not the alternate file name. For example, the command:
> mvn -f foo.xml install
> produces this error message:
> Cannot execute mojo: resources. It requires a project with an existing pom.xml, but the build is not using one.
> This error message is confusing and incorrect. Maven should instead report that the file "foo.xml" could not be loaded.
--
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