[
https://issues.apache.org/jira/browse/IVY-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilles Scokart updated IVY-398:
-------------------------------
Fix Version/s: 2.0
> "Private" confs aren't really private.
> --------------------------------------
>
> Key: IVY-398
> URL: https://issues.apache.org/jira/browse/IVY-398
> Project: Ivy
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.4.1
> Environment: all
> Reporter: John Williams
> Fix For: 2.0
>
>
> I should have a unit test soon, but the gist of the problem is that private
> confs "leak" from dependencies to the module being resolved, so a conf in the
> current module with the same name as a private conf in a dependent module may
> not work right. This seems analogous to the kind of problems that would
> happen if Java allowed private methods to be overridden.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
