Maven 2 & 3
  1. Maven 2 & 3
  2. MNG-3779

Improve error message when trying to execute mojo with no pom.xml

    Details

    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.9, 2.1.0-M1
    • Fix Version/s: 3.0-beta-1
    • Component/s: Errors, Logging
    • Labels:
      None
    • Complexity:
      Intermediate
    • Number of attachments :
      0

      Description

      I've seen many users on the mailing lists or in my company who get this error message:

      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:

      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.

        Activity

        Hide
        Brett Porter added a comment -

        this confusing error is not shown in 3.0-alpha-5. However, the behaviour is now to say "build successful" against a stub project.

        I think lifecycle phases should fail in a clear way against non-existant pom.xml scenarios. The only goals that make sense without a POM are standalone ones (archetype:generate, etc.)

        Show
        Brett Porter added a comment - this confusing error is not shown in 3.0-alpha-5. However, the behaviour is now to say "build successful" against a stub project. I think lifecycle phases should fail in a clear way against non-existant pom.xml scenarios. The only goals that make sense without a POM are standalone ones (archetype:generate, etc.)
        Hide
        Benjamin Bentmann added a comment -

        Improved in r928903.

        Show
        Benjamin Bentmann added a comment - Improved in r928903 .

          People

          • Assignee:
            Benjamin Bentmann
            Reporter:
            sleberrig
          • Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: