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 "Maarten Coene (JIRA)" <ji...@apache.org> on 2007/03/22 22:24:32 UTC

[jira] Resolved: (IVY-442) Ivy should fail where dependency uses undefined configuration

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

Maarten Coene resolved IVY-442.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5

This should be fixed now in SVN.

> Ivy should fail where dependency uses undefined configuration
> -------------------------------------------------------------
>
>                 Key: IVY-442
>                 URL: https://issues.apache.org/jira/browse/IVY-442
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.4.1
>            Reporter: easyproglife
>         Assigned To: Maarten Coene
>            Priority: Critical
>             Fix For: 1.5
>
>
> If you specify an undefined configuration in dependency element conf attribue, ivy just continues silently.
> It takes long time on medium and large projects to identify the problem: the module is missing from the expected classpath.
> The correct behavior should be ivy failure or at least a warning message.

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