You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@buildr.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2011/07/06 10:20:21 UTC

[jira] [Commented] (BUILDR-560) POM.load should show a meaning full error message when a POM could not be parsed.

    [ https://issues.apache.org/jira/browse/BUILDR-560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060394#comment-13060394 ] 

Hudson commented on BUILDR-560:
-------------------------------

Integrated in Buildr-ci-build #235 (See [https://builds.apache.org/job/Buildr-ci-build/235/])
    

> POM.load should show a meaning full error message when a POM could not be parsed.
> ---------------------------------------------------------------------------------
>
>                 Key: BUILDR-560
>                 URL: https://issues.apache.org/jira/browse/BUILDR-560
>             Project: Buildr
>          Issue Type: Bug
>          Components: Dependency management
>            Reporter: Tammo van Lessen
>            Priority: Minor
>             Fix For: 1.4.5
>
>         Attachments: BUILDR-560.patch
>
>
> When using transitive() you may run into the situation that some pom in your local repo cannot be parsed (e.g. because it contains some weird HTML, telling you about an HTTP 302). Currently you will get a backtrace but not the affected filename. This should be included in order to get a chance to fix the local pom.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira