ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin (JIRA)" <j...@apache.org>
Subject [jira] Updated: (IVY-780) ivy properties defined in an include file not available in the file that includes it
Date Mon, 24 Mar 2008 19:23:25 GMT

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

Xavier Hanin updated IVY-780:
-----------------------------

    Fix Version/s: 2.0

I mark this to be fixed in 2.0, since we won't be able to change it later without risking
a backward compatibility risk we can afford only in 2.0.

I'm really in favour of "fixing" this, so unless somebody objects I'll consider everybody's
ok to change the current behaviour.

> ivy properties defined in an include file not available in the file that includes it
> ------------------------------------------------------------------------------------
>
>                 Key: IVY-780
>                 URL: https://issues.apache.org/jira/browse/IVY-780
>             Project: Ivy
>          Issue Type: Bug
>            Reporter: Shawn Castrianni
>             Fix For: 2.0
>
>
> Now that I check the code again, it seems that any property defined in an included file
is not available in the file in which it has been included. As long as we have an history
for the class (Jan 24, 2007) it has been like that. I'm not sure why though, I see no added
value in preventing included file to set properties in the including files.
> Do anybody see any reason behind this? Would it hurt to change that?
> Xavier

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


Mime
View raw message