ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tuomas Kiviaho (JIRA)" <>
Subject [jira] [Commented] (ACE-306) Pax runner based target server
Date Fri, 23 Nov 2012 09:08:58 GMT


Tuomas Kiviaho commented on ACE-306:

Hello Marcel,

What I meant to write was 'in addition' instead 'instead of' because it good to have a solution
such as ace-laucher that is self-reliant and works out-of-the-box. What I was after was to
have option 3) without having to use management agent. run-target infact uses also the management-agent
and not directly the fine-grained bundles so I had to skim though the management agent activator
in order to see what makes it tick (which bundles are started and what configurations given

The main reason I wrote this issue was that there wasn't really anything in the bin-build.xml
nor in the run-target to support the scenario 3). devserver on the other hand has a nice pax
runner environment and I think that target environment could be served similarly. Currently
I feel that the learning curve is a bit steep for us that are unable to appreciate the work
you've put in to make thing easier. :-)
> Pax runner based target server
> ------------------------------
>                 Key: ACE-306
>                 URL:
>             Project: ACE
>          Issue Type: New Feature
>            Reporter: Tuomas Kiviaho
> It would be nice to have an open set of bundles instead of using ace launcher that embeds
everything together and forces using felix framework. I suggest that similar pax runner environment
would be provided by the ant script as it is now done for devserver.
> As bonus the configuration can be done using cfg files instead of CLI parameters.
> A downside is that for small projects there will be more ace bundles than actual project
bundles which gives a messy appearance in console. This can be avoided using OSGi subsystems
in the future.

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