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 "Gilles Scokart (JIRA)" <ji...@apache.org> on 2007/06/20 20:23:26 UTC

[jira] Updated: (IVY-364) Default status behavior in StatusManager

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

Gilles Scokart updated IVY-364:
-------------------------------

    Fix Version/s: 2.0

> Default status behavior in StatusManager
> ----------------------------------------
>
>                 Key: IVY-364
>                 URL: https://issues.apache.org/jira/browse/IVY-364
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.4.1
>            Reporter: Stephane Bailliez
>            Priority: Trivial
>             Fix For: 2.0
>
>
> Looking at StatusManager and XmlIvyConfigurationParser.
> It is unclear whether or not a null default status is valid.
> The SAX code goes the extra step not to put null, yet the StatusManager deals with null by automatically setting the last element of the statuses (why is that ? so that means that order is relevant ? what's the rationale ? )
> Failing on null and checking that the default status is actually really on the provided list of statuses would be my preference.

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