[
https://issues.apache.org/jira/browse/IVY-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12547712
]
Xavier Hanin commented on IVY-650:
----------------------------------
Actually I'm surprised you don't get @author tags anymore, I still have them
:-) Anyway, if it works fine for you it's great, you have the perfect
environment to contribute more high quality patches :-)
BTW, this discussion has gone pretty far from the issue subject, I guess it
would have been better on the [EMAIL PROTECTED] mailing list (easier to search
through for people looking for information about eclipse dev). Next time we'll
do better :-)
> 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.
