maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <>
Subject [jira] Closed: (MNG-4617) Incorrect/misleading error message when typo in module section
Date Thu, 01 Apr 2010 16:58:22 GMT


Benjamin Bentmann closed MNG-4617.

    Resolution: Cannot Reproduce
      Assignee: Benjamin Bentmann

> Incorrect/misleading error message when typo in module section
> --------------------------------------------------------------
>                 Key: MNG-4617
>                 URL:
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Command Line
>    Affects Versions: 3.0-alpha-7
>            Reporter: Max Andersen
>            Assignee: Benjamin Bentmann
>         Attachments:
> I have a module in a folder called "tests"
> In the parent folder I put a pom with:
> <module>test</module>
> i.e. the folder name does not actually exist and the error received is:
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]   The project  (/Users/max/Documents/code/jbosstools/modular_build/test) has
1 error
> [ERROR]     Non-parseable POM /Users/max/Documents/code/jbosstools/modular_build/test:
only whitespace content allowed before start tag and not [ (position: START_DOCUMENT seen
[... @1:1) -> [Help 2]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please read the
following articles:
> [ERROR] [Help 1]
> [ERROR] [Help 2]
> I would say it would make better sense to check if the file actually exists and report
the file as not there instead of a parse error which send me on to a hunt for a typo in tests/pom.xml
(since I didn't spot the missing 's' for a while :)

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message