You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ace.apache.org by "Bram de Kruijff (JIRA)" <ji...@apache.org> on 2013/05/27 09:41:03 UTC
[jira] [Reopened] (ACE-242) Allow custom check/update policies to
be defined instead of default ones.
[ https://issues.apache.org/jira/browse/ACE-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bram de Kruijff reopened ACE-242:
---------------------------------
> Allow custom check/update policies to be defined instead of default ones.
> -------------------------------------------------------------------------
>
> Key: ACE-242
> URL: https://issues.apache.org/jira/browse/ACE-242
> Project: ACE
> Issue Type: Improvement
> Reporter: J.W. Janssen
> Assignee: Marcel Offermans
>
> The deployment-task project defines a service for the MA to allow it to check/update it to the latest (remote) version. In addition, it also defines tasks for checking/updating the MA. While these default implementations work fine in most situations, they cannot be easily exchanged for other check/update policies.
> A solution would be to split off the (frontend-)service to check/update a MA from the 'ace-deployment-task' project into a separate project. This way, we have an ability to replace the default check/update tasks with other implementations.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira