[
https://issues.apache.org/jira/browse/IVY-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xavier Hanin resolved IVY-780.
------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.0)
2.0-RC1
I've just fixed this issue, and understood why the variable container was
cloned thanks to a unit test which failed when I removed the cloning: cloning
was needed to avoid to override the value of settings variable like
ivy.settings.dir. Since the values of these variables needs to be local to the
settings file loaded, I had to introduce a variable container wrapper,
delegating variable storage to the wrapped instance for all variables but the
settings variables. Both unit tests (old one and newly introduced one) now pass
successfully.
> 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
> Assignee: Xavier Hanin
> Fix For: 2.0-RC1
>
>
> 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.
