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 "John Wu (JIRA)" <ji...@apache.org> on 2007/08/24 18:01:31 UTC

[jira] Created: (IVY-596) HOWTO - Resolve dependencies on demand

HOWTO - Resolve dependencies on demand
--------------------------------------

                 Key: IVY-596
                 URL: https://issues.apache.org/jira/browse/IVY-596
             Project: Ivy
          Issue Type: New Feature
          Components: Documentation
    Affects Versions: 1.4.1
         Environment: Windows XP, Ant 1.6.5
            Reporter: John Wu
            Priority: Minor
             Fix For: 1.4.1


Scenario: To run task A, B, C, etc, only a common set of jars/zips (the set D) is needed; to run task X, a large number of jars/zips (the set Y) is needed. In most cases, task A, B, C, etc will be run. And in very rare cases, task X needs to be performed.

Issue: We don't want ivy to resolve (and may retrieve) the jars/zips in set D and Y every time we run the ant task, due to the performance concern and our internal network latency.


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


[jira] Commented: (IVY-596) HOWTO - Resolve dependencies on demand

Posted by "John Wu (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/IVY-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12522594 ] 

John Wu commented on IVY-596:
-----------------------------

That request seems possible based on the description here (http://incubator.apache.org/ivy/history/trunk/configuration/modules.html). But, I couldn't find a concrete working example.


> HOWTO - Resolve dependencies on demand
> --------------------------------------
>
>                 Key: IVY-596
>                 URL: https://issues.apache.org/jira/browse/IVY-596
>             Project: Ivy
>          Issue Type: New Feature
>          Components: Documentation
>    Affects Versions: 1.4.1
>         Environment: Windows XP, Ant 1.6.5
>            Reporter: John Wu
>            Priority: Minor
>             Fix For: 1.4.1
>
>
> Scenario: To run task A, B, C, etc, only a common set of jars/zips (the set D) is needed; to run task X, a large number of jars/zips (the set Y) is needed. In most cases, task A, B, C, etc will be run. And in very rare cases, task X needs to be performed.
> Issue: We don't want ivy to resolve (and may retrieve) the jars/zips in set D and Y every time we run the ant task, due to the performance concern and our internal network latency.

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


[jira] Updated: (IVY-596) HOWTO - Resolve dependencies on demand

Posted by "John Wu (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/IVY-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Wu updated IVY-596:
------------------------

    Attachment: RetrieveOnDemand.rar

Solution example.

> HOWTO - Resolve dependencies on demand
> --------------------------------------
>
>                 Key: IVY-596
>                 URL: https://issues.apache.org/jira/browse/IVY-596
>             Project: Ivy
>          Issue Type: New Feature
>          Components: Documentation
>    Affects Versions: 1.4.1
>         Environment: Windows XP, Ant 1.6.5
>            Reporter: John Wu
>            Priority: Minor
>             Fix For: 1.4.1
>
>         Attachments: RetrieveOnDemand.rar
>
>
> Scenario: To run task A, B, C, etc, only a common set of jars/zips (the set D) is needed; to run task X, a large number of jars/zips (the set Y) is needed. In most cases, task A, B, C, etc will be run. And in very rare cases, task X needs to be performed.
> Issue: We don't want ivy to resolve (and may retrieve) the jars/zips in set D and Y every time we run the ant task, due to the performance concern and our internal network latency.

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


[jira] Commented: (IVY-596) HOWTO - Resolve dependencies on demand

Posted by "John Wu (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/IVY-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12522595 ] 

John Wu commented on IVY-596:
-----------------------------

Quote:
Ivy proposes two mechanism to only resolve/retrieve dependencies.  You can use configurations, or type of artefact.

The use of configurations will allow you to manage which modules are included in your resolution.  The type of artefact will not really change your resolutions, but will only retrieve the artefact with the right type.

Gilles


> HOWTO - Resolve dependencies on demand
> --------------------------------------
>
>                 Key: IVY-596
>                 URL: https://issues.apache.org/jira/browse/IVY-596
>             Project: Ivy
>          Issue Type: New Feature
>          Components: Documentation
>    Affects Versions: 1.4.1
>         Environment: Windows XP, Ant 1.6.5
>            Reporter: John Wu
>            Priority: Minor
>             Fix For: 1.4.1
>
>
> Scenario: To run task A, B, C, etc, only a common set of jars/zips (the set D) is needed; to run task X, a large number of jars/zips (the set Y) is needed. In most cases, task A, B, C, etc will be run. And in very rare cases, task X needs to be performed.
> Issue: We don't want ivy to resolve (and may retrieve) the jars/zips in set D and Y every time we run the ant task, due to the performance concern and our internal network latency.

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


[jira] Resolved: (IVY-596) HOWTO - Resolve dependencies on demand

Posted by "John Wu (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/IVY-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Wu resolved IVY-596.
-------------------------

    Resolution: Fixed

Solution: Two configurations (commons and demanding) are defined in the ivy file, and the conf attribute of each ivy retrieve tag in the build file is specified.

Attached is the example, based on ivy 1.4.1. I think it may be a good candidate to be added to the ivy tutorial examples.


> HOWTO - Resolve dependencies on demand
> --------------------------------------
>
>                 Key: IVY-596
>                 URL: https://issues.apache.org/jira/browse/IVY-596
>             Project: Ivy
>          Issue Type: New Feature
>          Components: Documentation
>    Affects Versions: 1.4.1
>         Environment: Windows XP, Ant 1.6.5
>            Reporter: John Wu
>            Priority: Minor
>             Fix For: 1.4.1
>
>
> Scenario: To run task A, B, C, etc, only a common set of jars/zips (the set D) is needed; to run task X, a large number of jars/zips (the set Y) is needed. In most cases, task A, B, C, etc will be run. And in very rare cases, task X needs to be performed.
> Issue: We don't want ivy to resolve (and may retrieve) the jars/zips in set D and Y every time we run the ant task, due to the performance concern and our internal network latency.

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