maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <j...@codehaus.org>
Subject [jira] Created: (MNG-4623) model parsing errors can be less helpful in Maven 3
Date Wed, 07 Apr 2010 04:59:23 GMT
model parsing errors can be less helpful in Maven 3
---------------------------------------------------

                 Key: MNG-4623
                 URL: http://jira.codehaus.org/browse/MNG-4623
             Project: Maven 2 & 3
          Issue Type: Improvement
          Components: Errors
    Affects Versions: 3.0-alpha-7
            Reporter: Brett Porter


I accidentally left out the <build> tag around extensions:

{code:xml}
  </dependencies>
...
  <extensions>
    <extension>
      <groupId>org.apache.maven.wagon</groupId>
      <artifactId>wagon-ssh-external</artifactId>
      <version>1.0-beta-6</version>
    </extension>
  </extensions>
...
  <distributionManagement>
{code}

In Maven 2.2.1 the error was long winded but included:
{code}
Reason: Parse error reading POM. Reason: Unrecognised tag: 'extensions' (position: START_TAG
seen ...</dependencies>\n  <extensions>... @18:15)  for project unknown at .../pom.xml
{code}

In Maven 3.0-SNAPSHOT, the error is:

{code}
[ERROR]     Non-parseable POM .../pom.xml: Duplicated tag: 'artifactId' (position: START_TAG
seen ...</groupId>\n      <artifactId>... @21:19) -> [Help 2]
{code}

While it points at the right section, the first is much more accurate about what the problem
was

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

        

Mime
View raw message