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] Commented: (ACE-32) Use Pax Runner to bootstrap ace platforms
Date Sat, 04 Jul 2009 08:54:47 GMT

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

Toni Menzel commented on ACE-32:
--------------------------------

Just decided that the "deployments" should be Pax Runner Profiles.
This way, a profile can be started with 
"./pax-run --profiles=org.apache.ace.server" for latest felix (1.8.1).

Once the ACE artifacts are deployed "somewhere" on a maven repository, we can also put the
profiles into the official ops4j repository so pax runner can start the ace setups out of
the box (no local ace sources/builds necessary)



> 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
>
> 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