incubator-ivy-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gilles Scokart (JIRA)" <j...@apache.org>
Subject [jira] Commented: (IVY-358) erase/unpublish from a file based resolver
Date Fri, 22 Dec 2006 07:38:21 GMT
    [ http://issues.apache.org/jira/browse/IVY-358?page=comments#action_12460398 ] 
            
Gilles Scokart commented on IVY-358:
------------------------------------

Wouldn't it be better to have an unpublish task ?

This kind of task is very dangerous with a share repository (where you don't know if an revision
is still usefull or not)), but would indeed be usefull for private and snapshot repository.

See also IVY-321.  



> erase/unpublish from a file based resolver
> ------------------------------------------
>
>                 Key: IVY-358
>                 URL: http://issues.apache.org/jira/browse/IVY-358
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.4, 1.4.1
>         Environment: Linux / Any
>            Reporter: Eric Crahen
>            Priority: Minor
>
> I have a use case in which I set up a resolver chain that goes like this :
>   <filebased-resolver>
>   <url-resolver>
> In order to make local changes to packages that I would otherwise
> resolve with the url resolver, I check out the source, and publish
> the override to my filebased resolver. This enables me to "override"
> locally certain packages for development.
> Now at some point those local changes are no longer needed, either
> I decide I don't need them, someone else has merged the changes
> up into the release that can be obtained from the url-resolver, whatever.
> At this point, I no longer need the local "override" in my filebased-resolver.
> What I would like to do is unpublish the artifact there. I don't want to go
> in by hand, and remove things from my cache or delete things manually
> from the file based resolver. 
> One solution would be something like in order to "unpublish" is would
> publish to a different resolver
> <unpublish-filebased-resolver>
> This resolver might be just like the filebased-resolve, except that it does the
> opposite. Instead of copying a local artifact to the resolver location, it "unpublishes"
> by locating the artifact in the filebased resolver and removes it. The verb publish
> means to delete the artifact with this resolver.
> What this lets me do is manage my overrides (which is really just artifacts)
> using ivy and not manually file hunting.
> I can write ant tasks that would just publish to the erasing/unpublish resolver
> in order to remove a local override.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message