ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin (JIRA)" <>
Subject [jira] Resolved: (IVY-398) "Private" confs aren't really private.
Date Wed, 25 Jun 2008 10:15:49 GMT


Xavier Hanin resolved IVY-398.

       Resolution: Cannot Reproduce
    Fix Version/s:     (was: 2.0)

Without further details I mark this as resolved. Please reopen with more details if needed.

> "Private" confs aren't really private.
> --------------------------------------
>                 Key: IVY-398
>                 URL:
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.4.1
>         Environment: all
>            Reporter: John Williams
> 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.

View raw message