ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Offermans (JIRA)" <>
Subject [jira] [Commented] (ACE-224) Make resource processors manageable
Date Thu, 06 Mar 2014 13:48:46 GMT


Marcel Offermans commented on ACE-224:

We now have Gogo commands that allow you to manage resource processors:

w = (cw)
$w lrp

That checks out a workspace, and lists all resource processors that are available in the workspace.
The work in ACE-373 already gave us the option to upgrade resource processors (which is simply
a matter of uploading a new version of a resource processor) so if you see multiple versions
being listed, the highest one is used. If you want to delete resource processors, they are
just artifacts, so you can simply remove them. For example:

w = (cw)
each ($w lrp) { $w da $it }

Will iterate over all the available resource processors and delete them.

I'm leaving this issue open though as a Vaadin UI issue, because there we don't have this
capability yet.

> Make resource processors manageable
> -----------------------------------
>                 Key: ACE-224
>                 URL:
>             Project: ACE
>          Issue Type: Wish
>          Components: Architecture, UI
>    Affects Versions: 0.8.0-incubator
>            Reporter: Bram de Kruijff
> As discussed on the mailing list a while back. Resource processors are not handled as
regular artifacts making it cumbersome dealing with them. Most notably you can create processor
artifacts through webui/rest, but you will never see them. As a result as a client you can
never know what processors are available and you can only delete available once if you know
the exact uri.
> [0]
> [1]

This message was sent by Atlassian JIRA

View raw message