[ http://issues.apache.org/jira/browse/IVY-364?page=comments#action_12461053 ] Xavier Hanin commented on IVY-364: ----------------------------------
I'd say that if you do not set the default status the last one will be used as default status, as documented here: http://www.jayasoft.org/ivy/doc/configuration/statuses.html So the extra step in XmlIvyConfigurationParser is not necessary. Since using the last status is what is documented with Ivy 1.4, I prefer keeping things like that. But I agree this need to be better documented and explained, as you suggest in IVY-362. > Default status behavior in StatusManager > ---------------------------------------- > > Key: IVY-364 > URL: http://issues.apache.org/jira/browse/IVY-364 > Project: Ivy > Issue Type: Bug > Components: Core > Affects Versions: 1.4.1 > Reporter: Stephane Bailliez > Priority: Trivial > > 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. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
