You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ace.apache.org by "J.W. Janssen (Created) (JIRA)" <ji...@apache.org> on 2012/03/30 18:04:26 UTC
[jira] [Created] (ACE-242) Allow custom check/update policies to be
defined instead of default ones.
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: J.W. Janssen
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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (ACE-242) Allow custom check/update policies to be
defined instead of default ones.
Posted by "Marcel Offermans (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Offermans closed ACE-242.
--------------------------------
Looks good to me.
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (ACE-242) Allow custom check/update policies to
be defined instead of default ones.
Posted by "J.W. Janssen (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ACE-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
J.W. Janssen resolved ACE-242.
------------------------------
Resolution: Fixed
Assignee: Marcel Offermans (was: J.W. Janssen)
Introduced a ace-deployment-task-base project for the deployment frontend service; the ace-deployment-task project provides the default check/update tasks.
Close if you're happy with this solution...
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira