You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-commits@incubator.apache.org by "Maarten Coene (JIRA)" <ji...@apache.org> on 2007/04/06 13:47:32 UTC

[jira] Assigned: (IVY-77) Hide private or specific conf when publishing

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

Maarten Coene reassigned IVY-77:
--------------------------------

    Assignee: Maarten Coene  (was: Xavier Hanin)

> Hide private or specific conf when publishing
> ---------------------------------------------
>
>                 Key: IVY-77
>                 URL: https://issues.apache.org/jira/browse/IVY-77
>             Project: Ivy
>          Issue Type: New Feature
>          Components: Core
>            Reporter: veronique dupierris
>         Assigned To: Maarten Coene
>            Priority: Minor
>
> When publishing a module it could be nice to choose which conf to publish or not. Or, at least, be able to hide "private" conf. 
> Private conf, which should not be accessible by others modules, should not be visible in the ivy.xml files. The other  issue is that the list of dependencies displayed contains all dependencies even those  specific to provate conf which should never be retrieve.
> Module A  ivy.conf
>  <configurations>
>   <conf name="default" />
>   <conf name="dev" visibility="private" extends="default" />
> </configurations>
> <dependencies>
>  <dependency org="" name="junit" rev="3.8.1" conf="dev->*"/>
>  <dependency org="" name="log4j" rev="1.2.9" />
> </dependencies>
> Published Module A ivy conf :
>   <configurations>
>   <conf name="default" />  
> </configurations>
> <dependencies>
>  <dependency org="" name="log4j" rev="1.2.9" />
> </dependencies>

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