ace-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Offermans (JIRA)" <j...@apache.org>
Subject [jira] Commented: (ACE-32) Use Pax Runner to bootstrap ace platforms
Date Wed, 15 Jul 2009 13:51:14 GMT

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

Marcel Offermans commented on ACE-32:
-------------------------------------

Seems to be working just fine, all bundles start without problems both on Equinox and Felix.
Great work Toni! The next step is to apply a similar patch to the other targets we use. My
suggestion there would be to upgrade the targets we actively use instead of all of them (perhaps
throwing away unused ones finally).

> 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
>            Assignee: Marcel Offermans
>         Attachments: 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.


Mime
View raw message