ace-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Toni Menzel (JIRA)" <j...@apache.org>
Subject [jira] Updated: (ACE-32) Use Pax Runner to bootstrap ace platforms
Date Tue, 07 Jul 2009 00:01:14 GMT

     [ https://issues.apache.org/jira/browse/ACE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Toni Menzel updated ACE-32:
---------------------------

    Attachment: ace32-1.patch

Patch adds two new things to the "ant package" phase for dev-server.
I just went for one particuar target to let you cross check which direction we go and what
to expect.

1. core/deploy/target/dev-server/paxrunner/
A folder with just a script that calls the original pax runner at runtime.
just call "./run.sh" on the folder stated above. 

2. core/deploy/target/dev-server/standalone
this calls pax runner at build-time (inside ant) and let it construct a particuar platform
output.
The final folder contains routly (or should at least) an output that very much looks like
the current target output.
So, you also can call "run.sh" here. Look inside to see that there is no pax runner involved
anymore.
Benefit when compared to the current approach: framework independence

Where is the configuration ?
No real user configuration is done in the build scripts.
All configurations are read from core/conf/<target>/
For Pax Runner we have two configurations there:
--> platform.setup
There you specify the normal pax runner options. This includes the selection of the framework
(felix,equinox,knopflerfish,concierge)
and its versions.
--> platform.properties
additional properties that are needed to be configured as "environment" properties (-D)
like http.port and others.


> 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
>         Attachments: ace32-1.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