ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gintas Grigelionis (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IVY-393) Add "transitive" attribute to <cachepath>, <cachefileset> and <retrieve>
Date Fri, 01 Sep 2017 16:56:00 GMT

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

Gintas Grigelionis updated IVY-393:
-----------------------------------
    Summary: Add "transitive" attribute to <cachepath>, <cachefileset> and <retrieve>
 (was: Add "transtive" attribute to <cachepath>, <cachefileset> and <retrieve>)

> Add "transitive" attribute to <cachepath>, <cachefileset> and <retrieve>
> ------------------------------------------------------------------------
>
>                 Key: IVY-393
>                 URL: https://issues.apache.org/jira/browse/IVY-393
>             Project: Ivy
>          Issue Type: New Feature
>          Components: Ant, Core
>    Affects Versions: 1.4.1
>         Environment: all
>            Reporter: John Williams
>            Priority: Minor
>
> It would be useful to have a "transitive" option similar, but not identical, to the "transitive"
attribute of configurations.  Why not identical?  If there are two configurations that are
identical except that one is transitive and the other is not, the two configurations can choose
different revisions for some modules due to conflict resolution.  (For instance, if my module
depends on modA-1.0 and modB-1.0, and modB-1.0 depends on modA-1.1, the transitive config
will use modA-1.1 and the other config will use modA-1.0.)  The option for <cachepath>,
etc. should exclude indirect dependencies without affecting which revision is used.
> My rationale for this feature is that I would really like to have two classpaths--one
for compile time and the other for run time--that are identical except that the compile-time
classpath would have only direct dependencies.  I like having only direct dependencies at
compile time because it ensures that all the direct dependencies are declared to Ivy, but
the versions of all modules *must* be the same as the run-time classpath in order to avoid
causing a lot of confusion.  (A lesser reason for preferring a classpath with only direct
dependencies is that javac is much faster with a small classpath.)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message