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, 05 Oct 2009 21:58:31 GMT


Toni Menzel commented on ACE-32:

Attached a patch that provides pax runner development and "production" targets for dev-gateway,
dev-server-filebasesd, dev-server-webui.

This can (and should) fully replace all target-*.xml files on core.

1. Flexible Development Targets
with "ant package" you will get pax runner based configuration scripts for the afromentioned
targets in the usual deploy/target/ folders.
(, runDev.bat)

2. Standalone Outputs (just as before, but flexible as paxrunner generates many things)
with "ant zip" a pax runner instance will pre-load all requirements and config files and zip
them up at the usual release folder.

3. Single Point of Entry
All target relevant configuration now sits in conf/{target}/ (just parameters)
and platform.setup (all bundles required as well as pax runner options).
Target Framework and Version "can" be set in but is super-configured by
settings made in "packageDevelopment" and "packageProduction" targets in build.xml.
(currently it is Felix 2.0.0)

> 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-October2009.patch, pax-runner-1.2.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