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

Posted to ivy-commits@incubator.apache.org by "Xavier Hanin (JIRA)" <ji...@apache.org> on 2007/03/07 17:37:24 UTC

[jira] Resolved: (IVY-417) bad parsing of poms with build plugins

     [ https://issues.apache.org/jira/browse/IVY-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xavier Hanin resolved IVY-417.
------------------------------

    Resolution: Fixed

I've added a junit test and it passes successfully. In real life it's working too with trunk version. So I mark this bug as resolved.

> bad parsing of poms with build plugins
> --------------------------------------
>
>                 Key: IVY-417
>                 URL: https://issues.apache.org/jira/browse/IVY-417
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.4.1
>            Reporter: Xavier Hanin
>             Fix For: 1.5
>
>
> When a pom contains build plugins, sometimes Ivy is lost and uses the id of the plugin as identifier, thus causing errors like:
> maven2: bad organisation found in http://www.ibiblio.org/maven2/org/mule/mule/1.3.3/mule-1.3.3.pom: expected='org.mule' found='org.codehaus.mojo'

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.