ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (IVY-720) Resolving for muyltiple configurations when one is not in the list of available configurations cases an error but does not abort the build
Date Thu, 07 Feb 2008 17:53:08 GMT

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

Xavier Hanin resolved IVY-720.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.0-beta-2

I've just checked in a new unit test and a fix, I hope I understood correctly. Now if you
call resolve with a configuration which is not defined by the module Ivy will halt the build
with a build exception.

> Resolving for muyltiple configurations when one is not in the list of available configurations
cases an error but does not abort the build
> ------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: IVY-720
>                 URL: https://issues.apache.org/jira/browse/IVY-720
>             Project: Ivy
>          Issue Type: Bug
>          Components: Ant, Core
>    Affects Versions: 2.0.0-beta-1
>            Reporter: Jim Adams
>            Assignee: Xavier Hanin
>             Fix For: 2.0.0-beta-2
>
>
> We have an environment where we always resolve for 2 configurations. Some of the ivy
files donot care about the second configuration so don't specify it in the <configurations>
area of the ivy.xml file. In Ant, performing ivy:resolve we see an error about an unknown
configuration but the build continues. The real problem is that the resolve metadata is now
incorrect. When we turn around and publish the result of the build all the version numbers
are left as latest.integration. If we add the configuration to the list of available configurations
then we don't get an error and the publish contains the versions that were resolved.

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


Mime
View raw message