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

Sebastian Schuberth commented on IVY-1367:
------------------------------------------

Just out of curiosity, this seems to have been fixed since August 2012, so why 
is this not in Ivy 2.3.0?

> Support Conditional Setting of a Property
> -----------------------------------------
>
>                 Key: IVY-1367
>                 URL: https://issues.apache.org/jira/browse/IVY-1367
>             Project: Ivy
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 2.2.0
>            Reporter: J.C. Hamlin
>            Assignee: Nicolas Lalevée
>            Priority: Minor
>             Fix For: trunk
>
>
> Please allow a way to make conditional use of environment variables in 
> ivysettings.xml. If the environment variable is set, then set the property, 
> otherwise, don't set the property. This can be generalized into a general 
> test to set a property only if another property is set.
> Something like this, where the "ifset" is the new attribute of the property 
> element.
>   <properties environment="env"/>
>   <property name="ivy.repos.server" value="${env.IVY_SERVER}" 
> override="false" ifset="env.IVY_SERVER" />
>   <property name="ivy.repos.server" value="http://ivy:8081"; override="false"/>
> In ant, you do something like this, which is very similar (but more verbose):
>   <condition property="ivy.repos.server" value="${env.IVY_SERVER}">
>     <isset property="env.IVY_SERVER"/>
>   </condition>
>   <property name="ivy.repos.server" value="http://ivy:8081"/>
> So, if a user defines an environment variable it will override the default 
> value provided by the system. And if the environment variable is not defined 
> in the environment, then the system default value can apply.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to