incubator-ivy-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Trump (JIRA)" <j...@apache.org>
Subject [jira] Commented: (IVY-650) add publish triggers to event system
Date Sun, 02 Dec 2007 19:19:43 GMT

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

Jason Trump commented on IVY-650:
---------------------------------

Thanks for the feedback, and for including the patch so quickly.  I do use Eclipse (which
stuck the @author tags in there), but I don't have the CheckStyle plugin installed, which
I think caused me to miss some of these points.  I'll be sure to address these issues (formatting,
@author, license header) on any patches I submit in the future.

> add publish triggers to event system
> ------------------------------------
>
>                 Key: IVY-650
>                 URL: https://issues.apache.org/jira/browse/IVY-650
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 2.0
>            Reporter: Jason Trump
>            Assignee: Xavier Hanin
>            Priority: Minor
>             Fix For: 2.0.0-beta-1
>
>         Attachments: ivy-650.patch
>
>
> currently only download and resolve events are supported for triggers.  publish events
would facilitate customized updates to artifacts  (manifest files, jar signing, watermarking,
etc), as well as custom notification and logging.
> for consistency with the existing events, the new events should probably be:
> pre-publish-artifact
> post-publish-artifact
> with the following common attributes:
> organisation
> module
> revision
> artifact
> type
> ext
> resolver:    the name of the target resolver
> file:             the absolute path of the data file for the artifact
> overwrite:  whether the publication will overwrite existing resources
> post-publish-artifact will have an additional attribute:
> status:        'successful' or 'failed'
> indicating success or failure.

-- 
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