Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ant.apache.org
Message-ID: <15302286.1201087413884.JavaMail.jira@brutus>
Date: Wed, 23 Jan 2008 03:23:33 -0800 (PST)
From: "Xavier Hanin (JIRA)" <jira@apache.org>
To: notifications@ant.apache.org
Subject: [jira] Assigned: (IVY-703) Review settings loading in Ant
In-Reply-To: <31603278.1200556355427.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Xavier Hanin reassigned IVY-703:
--------------------------------

    Assignee: Xavier Hanin

> Review settings loading in Ant
> ------------------------------
>
>                 Key: IVY-703
>                 URL: https://issues.apache.org/jira/browse/IVY-703
>             Project: Ivy
>          Issue Type: Improvement
>    Affects Versions: 2.0.0-beta-1
>            Reporter: Xavier Hanin
>            Assignee: Xavier Hanin
>
> This has already been discussed several times on the mailing lists, we need to review how the settings are loaded in Ant to make it easier for users.
> The last discussion I've found is:
> http://www.nabble.com/ivy%3Aconfigure-and-ivy%3Asettings-again...-td13394480.html
> In which I think the final accepted proposition was:
> http://www.nabble.com/Re%3A-ivy%3Aconfigure-and-ivy%3Asettings-again...-p13417344.html
> To sum it up here, the foreseen changes are:
> - Use a task instead of a type for settings
> - if no id is specified in a settings task then the default will be assigned. This default is of course the one used in any resolve or retrieve tasks without explicit ids.
> - a new override attribute on the settings task determines what happens if an id is not unique. The override attribute can be one of "true | false | notallowed" with notallowed being the default. The meaning of this attribute should be: 
>   - notallowed : an error is raised if a settings has already been defined with this id 
>   - true : the current settings will take precedence over any previously defined setting with this id 
>   - false : the current settings will not override a previously defined setting with this id

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