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 "Gilles Scokart (JIRA)" <ji...@apache.org> on 2007/07/24 08:47:31 UTC

[jira] Commented: (IVY-581) Optional dependencies description

    [ https://issues.apache.org/jira/browse/IVY-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514916 ] 

Gilles Scokart commented on IVY-581:
------------------------------------

You more or less do that using configurations.

You can define a configuration containing the 'mandatory' set of dependency, and then you place ever set of optional dependencies in his own configuration.

If you look in our ivy.xml for ivy project (http://svn.apache.org/repos/asf/incubator/ivy/core/trunk/ivy.xml), you will see that core is the minimal set of dependencies, while httpclient, oro, vfs and sftp are all optional dependencies that you need only if you want to use some particular features of ivy.

Did you need something more?

> Optional dependencies description
> ---------------------------------
>
>                 Key: IVY-581
>                 URL: https://issues.apache.org/jira/browse/IVY-581
>             Project: Ivy
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Nikita Salnikov-Tarnovski
>            Priority: Minor
>
> Now it is impossible to describe optional dependencies of the project. It would be nice to be able to look at ivy.xml file and to see which jars I might want for better usage of the given project. For example Spring has tons of optional dependencies, but the only place to know about them is Spring's documentation.

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