[ 
https://issues.apache.org/jira/browse/IVY-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506770#comment-13506770
 ] 

Yanus Poluektovich edited comment on IVY-1392 at 11/29/12 8:43 PM:
-------------------------------------------------------------------

Attached is a patch that provides a bare-bones implementation of this 
functionality. The patch is applicable to revision 1415344 of 
https://svn.apache.org/repos/asf/ant/ivy/core/trunk.
                
      was (Author: ypoluektovich):
    Attached is a patch that provides a bare-bones implementation of this 
functionality.
                  
> Optional <include> ivysettings directives
> -----------------------------------------
>
>                 Key: IVY-1392
>                 URL: https://issues.apache.org/jira/browse/IVY-1392
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Yanus Poluektovich
>            Priority: Minor
>         Attachments: optional-include.patch
>
>
> To allow for VCS-friendly customization of dependency resolution process, a 
> feature that allows for files referenced in an <include> directive of an 
> ivysettings.xml file to be missing without it triggering an error.
> With such a feature, it would be possible to write a global ivysettings.xml 
> file that references a default setup of resolvers/repositories for a project, 
> commit it into a VCS and then never edit it. Instead, an "optional include" 
> directive will point to a file with standardized name, say, 
> ivysettings-local.xml. The file may be missing (which results in the 
> project-default configuration being used), or a developer can create such a 
> file and define an alternative resolution configuration for his own use. The 
> VCS can be configured to ignore the ivysettings-local.xml file, thus 
> absolving the developer of the need to ensure manually at each check-in that 
> the file is not committed into the VCS.
> Currently, a similar feature is implemented for properties files. 
> Unfortunately, it is impossible to, for example, override a project-default 
> resolver with a user-specific one only via use of properties.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to