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] [Resolved] (IVY-122) Delivering files to cache only.
Date Wed, 27 Sep 2017 05:32:00 GMT

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

Gintas Grigelionis resolved IVY-122.
------------------------------------
       Resolution: Won't Fix
         Assignee: Gintas Grigelionis
    Fix Version/s: master

CacheResolver is deprecated.

> Delivering files to cache only.
> -------------------------------
>
>                 Key: IVY-122
>                 URL: https://issues.apache.org/jira/browse/IVY-122
>             Project: Ivy
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 1.3-RC1
>            Reporter: Matt Inger
>            Assignee: Gintas Grigelionis
>             Fix For: master
>
>
> Unless i'm missing somethign, there seems to be no standard way to deliver ivy files
and artifacts to just the
> user's local cache.  Instead, you have to setup the cache as a resolver, and publish
to that resolver.  This seems
> rather innefficient.  It would be more helpful to have an ivy task to this directly:
> <ivy:cache .... />
> This task would basically just place all the artifacts and the ivy file in your cache.
> This is helpful when you start a project, or when a developer does not have write access
to the
> master repository.  Consider this setup:
> 1.  Master Repository is on Node A
> 2.  Developers resolve dependencies using an url resolver (http) for the master repository
> 3.  Automated build server publishes via a file-system resolver to the master repository
> 4.  File System on Node A is NOT exported, and is unavailable to developers
> What you'd expect (and what you can, in fact, do with maven 1 or 2) is that a developer
would
> publish to the cache while doign development for several reasons:
> 1.  There is no version yet in the master repository
> 2.  The developer is working on multiple modules, and needs to publish a module to
> the cache so that another module can see those changes when it builds.
> Seems like it should be an easy thing to do (though I don't know the ivy code well),
> and would be very beneficial.
> PS:  I'm stuck on the development version, because 1.2a doesn't even let you use
> the cache directory as the base of a resolver.
> I'm willing to volunteer to do this, if someone points me in the right direction.



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

Mime
View raw message