ace-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Angelo van der Sijpt (JIRA)" <j...@apache.org>
Subject [jira] Commented: (ACE-32) Use Pax Runner to bootstrap ace platforms
Date Mon, 31 Aug 2009 17:51:32 GMT

    [ https://issues.apache.org/jira/browse/ACE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749552#action_12749552
] 

Angelo van der Sijpt commented on ACE-32:
-----------------------------------------

It would be nice to have two versions of each target: one 'release' version which is as stand-alone
as possible, featuring the Felix version of our choice, and a 'dev' version based on Pax Runner,
so we can do some tweaking at run time. Furthermore, we might want to add some additional
bundles to the dev version.

There are a lot of combinations we could dream up (see http://cwiki.apache.org/confluence/display/ACE/Overview+of+ACE+components
for some inspiration), but to support the demo material on the wiki at the moment, we will
need,
- server with deployment
- server with deployment and obr
- target with deployment

Note that this way, we don't have any demo's of the logging system, nor of the relaying capacities.
It would be good if we can make it really easy to add new targets (as in, just point out the
bundles that should be included).

> Use Pax Runner to bootstrap ace platforms
> -----------------------------------------
>
>                 Key: ACE-32
>                 URL: https://issues.apache.org/jira/browse/ACE-32
>             Project: Ace
>          Issue Type: New Feature
>            Reporter: Toni Menzel
>            Assignee: Marcel Offermans
>         Attachments: ACE-32-3.patch, ace32-2.patch, pax-runner-1.1.1.jar
>
>
> Currently, the codebase+ant scripts create a fixed set of felix "deployments". Because
Pax Runner:
> - eliminiates the need to create bulky config files (for felix)
> - enables the use of many more (new+old) felix versions and frameworks (equinox+knopflerfish)
> i think it is a good thing to at least offer.
> Contribution will probably include a changed build.xml that adds tasks to create an "pax
runner starter" folder.
> This includes predifined paxrunner.args files that should be functionally identical to
the current deployment-folders.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message