ace-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Toni Menzel (JIRA)" <>
Subject [jira] Commented: (ACE-32) Use Pax Runner to bootstrap ace platforms
Date Mon, 31 Aug 2009 18:11:32 GMT


Toni Menzel commented on ACE-32:

Agree with all but would like to annotate that "add new targets .. [by].. just point out the
bundles that should be included":

This is usually dead simple, but components in ace rely on configuration supplied by files
(currently), so it always involves adding certain configuration files.
But sure, adding a new target should be simple, and this is what i will concentrate on for
next patch proposal.
So, concrete targets to be created are not so relevant, just the "how we can create and mantain"
is important.

Thanks angelo for the input. Patch will be supplied when something is there to show ;)

> Use Pax Runner to bootstrap ace platforms
> -----------------------------------------
>                 Key: ACE-32
>                 URL:
>             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.

View raw message