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 Mon, 03 Dec 2007 01:06:43 GMT

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

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

I blew away my Eclipse project, checked out the sources from the new Ant SVN repository, and
installed the CheckStyle plugin.  Now everything works as expected -- when I add a class,
I get the license header, there's no author tag, and I see the CheckStyle errors in the problems
list.  Looks like the problem was on my end.

I don't remember, but I think I probably did "New Project" instead of using Import to load
the project into Eclipse.

> 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