ace-dev mailing list archives

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


Toni Menzel updated ACE-32:

    Attachment: ACE-32-3.patch

Patch that provides paxrunner deployments for the following targets:
- dev-server-filebased
- dev-server-webui
- dev-gateway

Configuration is (as before) in core/conf/dev-X/platform.setup and platform.config.

Definition is made in main build.xml now (no more wrestling in dev-*.xmls).
Because there are now more targets affected, built takes a bit longer (pax runner runs multiple
Because of this, all of ths has been moved out of the package target and into the new cummulative
So, package is old and package2 is new. Just with package2 you get the standalone and paxrunner
deployments for the afromentioned targets.

> 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