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-492) support atomic publish operation
Date Fri, 11 May 2007 07:16:15 GMT

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

Gilles Scokart commented on IVY-492:
------------------------------------

Why not just having a separated separated TransactionalFileResolver ?  We have a 0 dependency
rule for out-of-the box resolver, but not for 'optional' resolver.

Of curse, if we do that, we have anyway to find an implementation the begin, abort, commit.
 

We put an empty implementation for the classical resolver.  Alternatively, instead of adding
the three methods to the resolver interface, we could make it 'optional' by adding the three
methods in a subinterface of resolver or a to separated interface.

> support atomic publish operation
> --------------------------------
>
>                 Key: IVY-492
>                 URL: https://issues.apache.org/jira/browse/IVY-492
>             Project: Ivy
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Geoff Reedy
>
> Some resolver types (e.g. one that uses subversion) could benefit from publishing a module
as a single atomic transaction.  Currently, each artifact (and it's checksums) are published
as separate operations, if one of the artifact uploads fail (perhaps an artifact is missing
or another user is trying to publish the same version at the same time) the ivy repository
can be in an inconsistent state with a half published module.  In addition, if uploads are
logged many entries in the log are generated for a single logical operation.
> A possible implementation strategy is to add three new methods to the resolver interface:
> beginPublish(ModuleRevisionId)
> abortPublish()
> commitPublish()
> beginPublish would be called before publishing the artifacts of the module, abortPublish
would be called if there is an error while publishing the module, commitPublish would be called
if all artifacts were successfully published.  Existing resolvers could simple implement these
methods as no-ops to retain the present behavior.

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


Mime
View raw message