ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bram de Kruijff (JIRA)" <>
Subject [jira] [Commented] (ACE-395) Multi deployment package support at least by a predictable order
Date Mon, 22 Jul 2013 06:32:49 GMT


Bram de Kruijff commented on ACE-395:

Hi Andrej, 

thank you for your message. Sure we would like to collaborate and welcome all contribution!
AFAIK you are the first person I hear of that actually uses multiple agents. Under ACE-347
we actually consider dropping this feature in the new agent. Obviously this does not mean
we remove it from the current right away and you are welcome to discuss its merits and contribute
:) Enforcing order may be a nice improvement on the current mechanism and your other changes
sound like they might be of interest too. However, we need more detail and discuss them in

So, please use the mailinglist [0] for discussion and general questions and create separate
bug / improvement issues here.

Best regards,

> Multi deployment package support at least by a predictable order
> ----------------------------------------------------------------
>                 Key: ACE-395
>                 URL:
>             Project: ACE
>          Issue Type: Improvement
>          Components: Deployment
>            Reporter: Andrej Zachar
>            Priority: Blocker
> Dear Apache Ace committers!
> We would like to deploy multiple deployment packages managed by
that have cross references!
> The problem is that one deployment packages have some cross  references to other bundle
in the other deployment packages. If they are deployed in a wrong other, the whole application
is working.
> Image situation:
> Application deployment package
>  +bundle 1 (requires licence bundle that is available in the other deloyment package)
>  +bundle n (requires licence bundle)
> Licence deployment package
>  +licence bundle
> To solve this issue I have introduced a simple solution: an order that tells
which agent has priority over the other agent.
> This approach allows me to keep deployment packages isolated, but I can tell which deployment
package (more precious which agent) will deploy first. 
> For that reason I have also introduced many small improvements and before I will describe
them all I want to know If there is an interest to cooperate on this topic.
> Here is some overview of changes:
> 1. Deployment of fragments and large packages (introduced Time Outs param)
> 2. Improved logging
> 3. Simplified the configuration folder structure for  local agent's repositories
> Thank you very much for your answer.
> Best regards,
> Andrej

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:

View raw message