[
https://issues.apache.org/jira/browse/IVY-780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580484#action_12580484
]
Nascif Abousalh-Neto commented on IVY-780:
------------------------------------------
This problem got in our way when we tried to implement a multi-tier repository
system, where each development branch would have its own configuration that
would be linked together using include files. We thought our design would work
out of the box and it didn't because of this behavior.
Would be nice to see the expected behavior implemented.
> 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
>
> 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.
